-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the need for KubernetesResourceMappingProvider #3923
Comments
Relates to #3993 |
11 tasks
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Apr 27, 2022
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
11 tasks
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Oct 19, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Nov 14, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Nov 14, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Nov 14, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Nov 14, 2022
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Nov 16, 2022
manusa
pushed a commit
that referenced
this issue
Nov 21, 2022
manusa
pushed a commit
that referenced
this issue
Nov 21, 2022
manusa
pushed a commit
that referenced
this issue
Nov 21, 2022
manusa
pushed a commit
that referenced
this issue
Nov 21, 2022
manusa
pushed a commit
that referenced
this issue
Nov 21, 2022
manusa
added a commit
to manusa/quarkus
that referenced
this issue
Dec 20, 2022
Since Fabric8 Kubernetes Client 6.3, types are no longer automatically registered for deserialization. For automatic type registration an `META-INF/services/io.fabric8.kubernetes.api.model.KubernetesResource` SPI definition file needs to be provided instead with the Kubernetes Resources (Objects -HasMadata impls-) that need to be automatically registered in the KubernetesDeserializer. fabric8io/kubernetes-client#3923 Signed-off-by: Marc Nuri <[email protected]>
ebullient
pushed a commit
to maxandersen/quarkus
that referenced
this issue
Jan 24, 2023
Since Fabric8 Kubernetes Client 6.3, types are no longer automatically registered for deserialization. For automatic type registration an `META-INF/services/io.fabric8.kubernetes.api.model.KubernetesResource` SPI definition file needs to be provided instead with the Kubernetes Resources (Objects -HasMadata impls-) that need to be automatically registered in the KubernetesDeserializer. fabric8io/kubernetes-client#3923 Signed-off-by: Marc Nuri <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we can also do away with the need for KubernetesResourceMappingProvider - basically the same mechanism as what is registering handlers that is proposed by #3845 but via the ExtensionAdapter. All it needs to do is declare the packages of the models.
It all depends on the expectation of if the user can make use of KubernetesDesializer / Serialization independently of the client as that will complicate this simplification.
Originally posted by @shawkins in #3876 (comment)
The text was updated successfully, but these errors were encountered: