Release announcement for Fabric8-Kubernetes-Client 7.6.0

[Ashish Thakur]

Hi All,

We are pleased to announce Fabric8 Kubernetes Client 7.6.0 was just released. You can find the release at Maven Central [1].

These are the features and fixes included in 7.6.0:
- Fix #5292: Cluster() configuration should use tlsServerName [2]
- Fix #7174: (httpclient) Fix HTTP client factory priority - VertxHttpClientFactory (default) now has priority -1, OkHttpClientFactory restored to priority 0 [3]
- Fix #7174: (httpclient-vertx-5) Add runtime check for Vert.x 5 classes to provide clear error when Vert.x 4/5 conflict occurs [4]
- Fix #7174: (chaos-tests) Fix classpath conflict when testing with Vert.x 5 HTTP client [5]
- Fix #7415: (java-generator) Fix generic type erasure for array of enums with default values [6]
- Fix #7422: (okhttp) Remove internal API usage and fix deprecated OkHttp 5 calls [7]
- Fix #7446: making the timeout of BaseOperation.createOrReplace() configurable [8]
- Fix #1105: Add javadoc cross-linking for Fabric8 modules and external dependencies [9]
- Fix #5756: Use Editable interface instead of reflection to instantiate resource builders [10]
- Fix #7422: bump okhttp from 4.12.0 to 5.3.2 [11]
- Fix #7252: call additionalConfig when building Vert.x HTTP clients with VertxHttpClientFactory [12]
- Fix #7374: bump snakeyaml-engine from 2.10 to 3.0.1 [13]
- Fix #7385: Support for Kubernetes v1.35 (Timbernetes) [14]
- Fix #7174: Added Vert.x 5 HTTP client implementation with improved async handling and WebSocket separation [15]
- Fix #7402: Added Byte code level semver API compatibility report generation using Revapi [16]
- Fix #5756: Resources edited with visitors must now implement `io.fabric8.kubernetes.api.builder.Editable`. All model classes provided by the client already implement this interface. User-provided custom resources that use visitor-based editing will need to implement `Editable` (trivial when a builder already exists). [17]
- Fix #7422: bump okhttp from 4.12.0 to 5.3.2. The versions are binary compatible, but the major version upgrade might cause side effects. [18]
The `kubernetes-httpclient-vertx` (Vert.x 4.x) and `kubernetes-httpclient-vertx-5` (Vert.x 5.x) modules are **mutually exclusive**.
They must not be included together in your project dependencies.
Both modules provide an implementation of `HttpClient.Factory` and use the same `io.vertx` artifact coordinates but with incompatible major versions.
-*Problem**: If both modules are present on the classpath, Maven's dependency resolution may pick Vert.x 4.x JARs while the `Vertx5HttpClientFactory` is selected at runtime.
This causes `NoClassDefFoundError` for Vert.x 5-specific classes like `io.vertx.core.impl.SysProps`.
-*Solution**: Ensure your project includes only ONE of these modules:
- `kubernetes-httpclient-vertx` (default, uses Vert.x 4.x) - included transitively via `kubernetes-client`
- `kubernetes-httpclient-vertx-5` (optional, uses Vert.x 5.x) - requires explicit dependency and exclusion of vertx-4
When using Vert.x 5, exclude the default Vert.x 4 client and set the `vertx.version` property:
```xml
<properties>
  <vertx.version>${vertx5.version}</vertx.version> <!-- or explicit 5.0.7 -->
</properties>
<dependencies>
  <dependency>
    <groupId>io.fabric8</groupId>
    <artifactId>kubernetes-client</artifactId>
    <exclusions>
      <exclusion>
        <groupId>io.fabric8</groupId>
        <artifactId>kubernetes-httpclient-vertx</artifactId>
      </exclusion>
    </exclusions>
  </dependency>
  <dependency>
    <groupId>io.fabric8</groupId>
    <artifactId>kubernetes-httpclient-vertx-5</artifactId>
  </dependency>
</dependencies>
```

Your feedback is highly appreciated, you can provide it replying to the mailing list or through the usual channels. [20] [21]

[1] https://repo1.maven.org/maven2/io/fabric8/kubernetes-client/7.6.0/
[2] https://github.com/fabric8io/kubernetes-client/issues/5292
[3] https://github.com/fabric8io/kubernetes-client/issues/7174
[4] https://github.com/fabric8io/kubernetes-client/issues/7174
[5] https://github.com/fabric8io/kubernetes-client/issues/7174
[6] https://github.com/fabric8io/kubernetes-client/issues/7415
[7] https://github.com/fabric8io/kubernetes-client/issues/7422
[8] https://github.com/fabric8io/kubernetes-client/issues/7446
[9] https://github.com/fabric8io/kubernetes-client/issues/1105
[10] https://github.com/fabric8io/kubernetes-client/issues/5756
[11] https://github.com/fabric8io/kubernetes-client/issues/7422
[12] https://github.com/fabric8io/kubernetes-client/issues/7252
[13] https://github.com/fabric8io/kubernetes-client/issues/7374
[14] https://github.com/fabric8io/kubernetes-client/issues/7385
[15] https://github.com/fabric8io/kubernetes-client/issues/7174
[16] https://github.com/fabric8io/kubernetes-client/issues/7402
[17] https://github.com/fabric8io/kubernetes-client/issues/5756
[18] https://github.com/fabric8io/kubernetes-client/issues/7422
[19] https://github.com/fabric8io/kubernetes-client/issues/7174
[20] https://github.com/fabric8io/kubernetes-client
[21] https://gitter.im/fabric8io/kubernetes-client