Update fabric8-kubernetes-client monorepo to v6.9.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.fabric8:crd-generator-apt	6.7.2 -> 6.9.1
io.fabric8:kubernetes-httpclient-okhttp	6.7.2 -> 6.9.1

---

Release Notes

fabric8io/kubernetes-client (io.fabric8:crd-generator-apt)

v6.9.1

Bugs

• Fix #​5501: (crd-generator) Fix fallback value of Default annotation in presence of multiple accessors
• Fix #​5522: type inference fixed by bumping Sundrio to 0.101.2 (see https://github.com/sundrio/sundrio/pull/431)
• Fix #​5554: move certificates in kubernetes-client-api to avoid collisions with those from mockwebserver

v6.9.0

Bugs

• Fix #​5466: OperationSupport should not fail trying to parse Status
• Fix #​5382: (java-generator) Allow to deserialize more valid RFC3339 date-time and make the format customizable
• Fix #​5380: (java-generator) Avoid to emit Java Keywords as package names
• Fix #​5457: (java-generator) Correctly handle numeric enums
• Fix #​5379: ensuring informOnCondition and waitUntilCondition commple with exception when the client closes
• Fix #​5463: ensures that onStopLeading is called with releaseOnCancel even when leadership is already lost
• Fix #​5423: OkHttpClientImpl supports setting request method for empty payload requests

Improvements

• Fix #​5316: support read-only system KeyStores with Kube CA Certs
• Fix #​5327: added proactive shutdown of informers on client close
• Fix #​5432: (java-generator) Add the possibility to always emit additionalProperties on generated POJOs
• Fix #​5410: (crd-generator) added support for default
• Fix #​5368: added support for additional ListOptions fields
• Fix #​5377: added a createOr and unlock function to provide a straight-forward replacement for createOrReplace.
• Fix #​4624: added Config.onlyHttpWatches to control whether watches should only use regular HTTP requests, and not attempt WebSocket connections.
• Fix #​5388: (crd-generator) Generate deterministic CRDs
• Fix #​5135: added per instance methods to create a builder - instead on new PodBuilder(pod), you may use pod.toBuilder()
• Fix #​5257: Add ErrorStreamMessage and StatusStreamMessage to ease mocking of pods/exec requests
• Fix #​5220: refinements and clarifications to the validation of names

Dependency Upgrade

• Fix #​5286: Update Fabric8 OpenShift Model as per OpenShift 4.13.12
• Fix #​5373: Gradle base API based on v8.2.1
• Fix #​5401: Upgrade Fabric8 Kubernetes Model to Kubernetes v1.28.2

New Features

• Fix #​5430: Mock Web Server migrated to this repository

Note: Breaking changes

• Fix #​5343: Removed io.fabric8.kubernetes.model.annotation.PrinterColumn, use io.fabric8.crd.generator.annotation.PrinterColumn
• Fix #​5368: ListOptions parameter ordering is now alphabetical. If you are using non-crud mocking for lists with options, you may need to update your parameter order.
• Fix #​5391: Removed the vertx-uri-template dependency from the vertx client, if you need that for your application, then introduce your own dependency.
• Fix #​5220: KubernetesResourceUtil.isValidLabelOrAnnotation has been deprecated because the rules for labels and annotations are different

v6.8.1

Bugs

• Fix #​5382: (java-generator) Allow to deserialize more valid RFC3339 date-time and make the format customizable
• Fix #​5380: (java-generator) Avoid to emit Java Keywords as package names

v6.8.0

Bugs

• Fix #​4225: [crd-generator] Principled generation of enum values instead of considering more properties
• Fix #​5113: Clashing package names in trigger model dependencies
• Fix #​5186: Support for Pod uploads with big numbers
• Fix #​5221: Empty kube config file causes NPE
• Fix #​5281: Ensure the KubernetesCrudDispatcher's backing map is accessed w/lock
• Fix #​5298: Prevent requests needing authentication from causing a 403 response
• Fix #​5327: Ensured that the informer reconnect task terminates after client close

Improvements

• Fix #​5166: Remove opinionated messages from Config's errorMessages and deprecate it
• Fix #​5233: Generalized SchemaSwap to allow for cycle expansion
• Fix #​5262: all built-in collections will omit empty in their serialized form.
• Fix #​5287: Add an option to filter the files processed by the java-generator, based on a suffix allowlist
• Fix #​5293: Mock server supports KubernetesClientBuilder customization
• Fix #​5315: Introduced kubernetes-junit-jupiter-autodetect to use with automatic extension registration
• Fix #​5339: @PrinterColumn annotation has configuration field for priority

Dependency Upgrade

• Fix #​5056: Update Kubernetes Model to v1.27.3
• Fix #​5140: Upgrade Fabric8 Knative Extension Model to v0.37.1
• Fix #​5308: sundrio was updated to the latest version. FluentImpl classes were removed, along with methods that had been previously deprecated. Some seldom used builder methods dealing manipulating buildable fields as a subtype such as withXXXField were removed in favor of using more general methods such as withField.

New Features

• Fix #​5133: Support for using TokenRequest for existing ServiceAccount

Note: Breaking changes

• Fix #​2718: KubernetesResourceUtil.isResourceReady was deprecated. Use client.resource(item).isReady() or Readiness.getInstance().isReady(item) instead.
• Fix #​5171: Removed Camel-K extension, use org.apache.camel.k:camel-k-crds instead.
• Fix #​5262: Built-in resources were in-consistent with respect to their serialization or empty collections. In many circumstances this was confusing behavior. In order to be consistent all built-in resources will omit empty collections by default. This is a breaking change if you are relying on an empty collection in a json merge or a strategic merge where the list has a patchStrategy of atomic. In these circumstances the empty collection will no longer be serialized. You may instead use a json patch, server side apply instead, or modify the serialized form of the patch.
• Fix #​5279: (java-generator) Add native support for date-time fields, they are now mapped to native java.time.ZonedDateTime
• Fix #​5315: kubernetes-junit-jupiter no longer registers the NamespaceExtension and KubernetesExtension extensions to be used in combination with junit-platform.properties>junit.jupiter.extensions.autodetection.enabled=trueconfiguration. If you wish to use these extensions and autodetect them, change your dependency to kubernetes-junit-jupiter-autodetect.
• Deprecating io.fabric8.kubernetes.model.annotation.PrinterColumn in favor of: io.fabric8.crd.generator.annotation.PrinterColumn
• Resource classes in resource.k8s.io/v1alpha1 have been moved to resource.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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[stefanbethke]

Doesn't work as the operator framework still requires 6.7.2 (and will break with 6.9.1). When the operator framework gets updated, we will update the kubernetes client as well.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (6.9.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.