Fix #3733: The authentication command from the .kube/config won't be discarded if no arguments are specified
Fix #4312: fix timestamp can't be deserialized for IstioCondition
Fix #4369: Informers will retry with a backoff on list/watch failure as they did in 5.12 and prior.
Fix #4350: SchemaSwap annotation is now repeatable and is applied multiple times if classes are used more than once in the class hierarchy.
Fix #3733: The authentication command from the .kube/config won't be discarded if no arguments are specified
Fix #4441: corrected patch base handling for the patch methods available from a Resource - resource(item).patch() will be evaluated as resource(latest).patch(item). Also undeprecated patch(item), which is consistent with leaving patch(context, item) undeprecated as well. For consistency with the other operations (such as edit), patch(item) will use the context item as the base when available, or the server side item when not. This means that patch(item) is only the same as resource(item).patch() when the patch(item) is called when the context item is missing or is the same as the latest.
Fix #4365: The Watch retry logic will handle more cases, as well as perform an exceptional close for events that are not properly handled. Informers can directly provide those exceptional outcomes via the SharedIndexInformer.stopped CompletableFuture.
Fix #4396: Provide more error context when @Group/@Version annotations are missing
Fix #4384: The Java generator now supports the generation of specific annotations (min, max, pattern, etc.), as defined by #4348
Fix #4408: Allowing informers started via the start() method to have configurable exception / retry handling.
Fix #3864: Change ManagedOpenShiftClient OSGi ConfigurationPolicy to REQUIRE
Fix #4470: Added timestamps support for deployment logs and other resources.
Fix #4476: [crd-generator] Support custom Annotations and Labels to be emitted in the CRD
Dependency Upgrade
Fix #4243: Update Tekton pipeline model to v0.39.0
Fix #4243: Update Tekton triggers model to v0.20.2
Fix #4398: add annotation @PreserveUnknownFields for marking generated field have x-kubernetes-preserve-unknown-fields: true defined
Fix #4351: add javax.annotation.processing.Generated to classes generated with the java-generator
Note: Breaking changes in the API
Fix #4350: SchemaSwap's fieldName parameter now expects a field name only, not a method or a constructor.
Module io.fabric8:tekton-model-triggers which contained Tekton triggers v1alpha1 model has been removed. We have introduced separate modules io.fabric8:tekton-model-v1alpha1 and io.fabric8:tekton-model-v1beta1 for Tekton triggers v1alpha1 and v1beta1 apigroups respectively. Users who are using io.fabric8:tekton-client dependency directly should be unaffected by this change.
Fix #3864: Now it's compulsory to provide etc/io.fabric8.openshift.client.cfg file in order to load ManagedOpenShiftClient in OSGi environment.
Fix #3924: Extension Mock modules have been removed
Fix #4384: javax.validation.* annotations are no longer added by the Java generator.
Fix #3906: removed BaseKubernetesList, use KubernetesList instead
Fix #4408: deprecated SharedInformerFactory.addSharedInformerEventListener, instead use the SharedIndexInformer.stopped method. Also the signature of SharedIndexInformer.start was changed to a CompletionStage rather than a CompletableFuture.
Fix #3733: The authentication command from the .kube/config won't be discarded if no arguments are specified
Fix #4312: fix timestamp can't be deserialized for IstioCondition
Fix #4369: Informers will retry with a backoff on list/watch failure as they did in 5.12 and prior.
Fix #4350: SchemaSwap annotation is now repeatable and is applied multiple times if classes are used more than once in the class hierarchy.
Fix #3733: The authentication command from the .kube/config won't be discarded if no arguments are specified
Fix #4441: corrected patch base handling for the patch methods available from a Resource - resource(item).patch() will be evaluated as resource(latest).patch(item). Also undeprecated patch(item), which is consistent with leaving patch(context, item) undeprecated as well. For consistency with the other operations (such as edit), patch(item) will use the context item as the base when available, or the server side item when not. This means that patch(item) is only the same as resource(item).patch() when the patch(item) is called when the context item is missing or is the same as the latest.
Fix #4365: The Watch retry logic will handle more cases, as well as perform an exceptional close for events that are not properly handled. Informers can directly provide those exceptional outcomes via the SharedIndexInformer.stopped CompletableFuture.
Fix #4396: Provide more error context when @Group/@Version annotations are missing
Fix #4384: The Java generator now supports the generation of specific annotations (min, max, pattern, etc.), as defined by #4348
Fix #4408: Allowing informers started via the start() method to have configurable exception / retry handling.
Fix #3864: Change ManagedOpenShiftClient OSGi ConfigurationPolicy to REQUIRE
Fix #4470: Added timestamps support for deployment logs and other resources.
Fix #4476: [crd-generator] Support custom Annotations and Labels to be emitted in the CRD
Dependency Upgrade
Fix #4243: Update Tekton pipeline model to v0.39.0
Fix #4243: Update Tekton triggers model to v0.20.2
Fix #4398: add annotation @PreserveUnknownFields for marking generated field have x-kubernetes-preserve-unknown-fields: true defined
Fix #4351: add javax.annotation.processing.Generated to classes generated with the java-generator
Note: Breaking changes in the API
Fix #4350: SchemaSwap's fieldName parameter now expects a field name only, not a method or a constructor.
Module io.fabric8:tekton-model-triggers which contained Tekton triggers v1alpha1 model has been removed. We have introduced separate modules io.fabric8:tekton-model-v1alpha1 and io.fabric8:tekton-model-v1beta1 for Tekton triggers v1alpha1 and v1beta1 apigroups respectively. Users who are using io.fabric8:tekton-client dependency directly should be unaffected by this change.
Fix #3864: Now it's compulsory to provide etc/io.fabric8.openshift.client.cfg file in order to load ManagedOpenShiftClient in OSGi environment.
Fix #3924: Extension Mock modules have been removed
Fix #4384: javax.validation.* annotations are no longer added by the Java generator.
Fix #3906: removed BaseKubernetesList, use KubernetesList instead
Fix #4408: deprecated SharedInformerFactory.addSharedInformerEventListener, instead use the SharedIndexInformer.stopped method. Also the signature of SharedIndexInformer.start was changed to a CompletionStage rather than a CompletableFuture.
... (truncated)
Commits
43b6793 [RELEASE] Updated project version to v6.2.0
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps kubernetes-client from 5.12.2 to 6.2.0.
Release notes
Sourced from kubernetes-client's releases.
... (truncated)
Changelog
Sourced from kubernetes-client's changelog.
... (truncated)
Commits
43b6793[RELEASE] Updated project version to v6.2.0d74a60bchore: update changelogdc5c8c3Customizable annotations and labels on CRD (#4476)b025aeffix #4496: removing list handling from watchingf8dd11bfix: incorrect type6bb2de9fix #4408: deprecating addSharedInformerEventListener5f6a11afix #4408: allowing for users to set the exception handling behavior00cf3fdRefactored operation contexts.e04de76fix #3906: fully regenerating the modelsad718e6fix #3906: removing BaseKubernetesListDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)