Update dependency io.fabric8:kubernetes-client to v6 (4.0.x) - autoclosed #319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.10.2
->6.9.2
Release Notes
fabric8io/kubernetes-client (io.fabric8:kubernetes-client)
v6.9.2
Compare Source
Bugs
v6.9.1
Compare Source
Bugs
Default
annotation in presence of multiple accessorsv6.9.0
Compare Source
Bugs
Improvements
additionalProperties
on generated POJOsdefault
Dependency Upgrade
New Features
Note: Breaking changes
io.fabric8.kubernetes.model.annotation.PrinterColumn
, useio.fabric8.crd.generator.annotation.PrinterColumn
v6.8.1
Compare Source
Bugs
v6.8.0
Compare Source
Bugs
Improvements
errorMessages
and deprecate itkubernetes-junit-jupiter-autodetect
to use with automatic extension registration@PrinterColumn
annotation has configuration field for priorityDependency Upgrade
New Features
Note: Breaking changes
client.resource(item).isReady()
orReadiness.getInstance().isReady(item)
instead.org.apache.camel.k:camel-k-crds
instead.date-time
fields, they are now mapped to nativejava.time.ZonedDateTime
junit.jupiter.extensions.autodetection.enabled=true
configuration. If you wish to use these extensions and autodetect them, change your dependency tokubernetes-junit-jupiter-autodetect
.io.fabric8.kubernetes.model.annotation.PrinterColumn
in favor of:io.fabric8.crd.generator.annotation.PrinterColumn
resource.k8s.io/v1alpha1
have been moved toresource.k8s.io/v1alpha2
apiGroup in Kubernetes 1.27. Users are required to change package of the following classes:io.fabric8.kubernetes.api.model.resource.v1alpha1.PodSchedulingContext
-> -io.fabric8.kubernetes.api.model.resource.v1alpha2.PodSchedulingContext
io.fabric8.kubernetes.api.model.resource.v1alpha1.ResourceClaim
-> -io.fabric8.kubernetes.api.model.resource.v1alpha2.ResourceClaim
io.fabric8.kubernetes.api.model.resource.v1alpha1.ResourceClaimTemplate
->io.fabric8.kubernetes.api.model.resource.v1alpha2.ResourceClaimTemplate
io.fabric8.kubernetes.api.model.resource.v1alpha1.ResourceClass
->io.fabric8.kubernetes.api.model.resource.v1alpha2.ResourceClass
v6.7.2
Compare Source
Bugs
io.fabric8.tekton.triggers.internal.knative.pkg.apis.duck.v1beta1
in tekton v1beta1 triggers modelv6.7.1
Compare Source
Bugs
v6.7.0
Compare Source
Bugs
additionalProperties: true
emitting a field of typeAnyType
Improvements
Dependency Upgrade
New Features
Note: Breaking changes
v6.6.2
Compare Source
Bugs
Fix #5121: RequestConfig is propagated to derived HttpClient instances
v6.6.1
Compare Source
Bugs
v6.6.0
Compare Source
Bugs
v1alpha
apigroup packages inistio-model-v1beta1
Improvements
batch/v1
CronJob insteadsubresource
settingNamespaceVisitFromServerGetWatchDeleteRecreateWaitApplicableListImpl
extendsServerSideApplicable
Dependency Upgrade
New Features
Note: Breaking changes
v6.5.1
Compare Source
Bugs
idp-certificate-authority-data
absent in auth-provider config403
response codev6.5.0
Compare Source
Bugs
http://json-schema.org/draft-07/schema#
)NullPointerException
inThread.currentThread().getContextClassLoader()
*/
in generated JavaDocsImprovements
PUT
andPATCH
requests.scope
field when implementing theNamespaced
interfacekubernetes-examples/
module to use up to date codenetworking.k8s.io
apiGroup while resolving IngressDependency Upgrade
New Features
Note: Breaking changes
replace
is deprecated, you should useupdate
instead. If you set the resourceVersion to null it will not be optimistically locked.createOrReplace
is deprecated, you should use server side apply instead.edit
uses now optimistic locking by default. To disable locking you should change your methods to follow this pattern:.edit(pod -> new PodBuilder(pod).editMetadata().withResourceVersion(null)//...
Note: Deprecations
v6.4.1
Compare Source
Bugs
v6.4.0
Compare Source
Bugs
CompletableFuture
cancel will close / cancel the underlying resourceImprovements
New Features
Note: Breaking changes
v6.3.1
Compare Source
Bugs
v6.3.0
Compare Source
Bugs
isSupported
doesn't check all the applicable API GroupsImprovements
New Features
Note: Breaking changes
javax.validation.constraints.NotNull
in thecrd-generator
, to mark a property asrequired
it needs to be annotated withio.fabric8.generator.annotation.Required
v6.2.0
Compare Source
Bugs
Improvements
TokenRefreshInterceptor
Annotations
andLabels
to be emitted in the CRDDependency Upgrade
New Features
x-kubernetes-preserve-unknown-fields: true
definedjavax.annotation.processing.Generated
to classes generated with thejava-generator
Note: Breaking changes in the API
io.fabric8:tekton-model-triggers
which contained Tekton triggers v1alpha1 model has been removed. We have introduced separate modulesio.fabric8:tekton-model-v1alpha1
andio.fabric8:tekton-model-v1beta1
for Tekton triggers v1alpha1 and v1beta1 apigroups respectively. Users who are usingio.fabric8:tekton-client
dependency directly should be unaffected by this change.Configuration
📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.