Fabric8 Kubernetes Client 7.9 is now available!

On behalf of the Fabric8 team and everyone who has contributed, I'm happy to announce that the Fabric8 Kubernetes Client 7.9.0 has been released and is now available from Maven Central 🎉.

This marks the ninth minor release of the Fabric8 Kubernetes Client 7, bringing new features, bug fixes, and improvements while keeping the breaking changes minimal.

Thanks to all of you who have contributed with issue reports, pull requests, feedback, and spreading the word with blogs, videos, comments, and so on. We really appreciate your help, keep it up!

Looking ahead to 8.0

With 7.x settling into maintenance, we're shifting our focus to the next major version, Fabric8 Kubernetes Client 8.0. The three headline changes we're planning are:

• A new JDK baseline: the minimum required version moves up to Java 17, so Java 11 will no longer be supported.
• A migration to Jackson 3.x, replacing the current Jackson 2.x serialization stack.
• A new default HTTP client: the transport switches from Vert.x 4 to Vert.x 5.

We'll share more details as 8.0 takes shape, so keep an eye out and start planning your upgrade path if any of these changes affect your setup.

What's new?

Without further ado, let's have a look at the most significant updates:

• Kubernetes 1.37 support (Garhwal)
• Gateway API 1.6 with TCPRoute and UDPRoute
• WebSocket reliability on the Vert.x 5 and Jetty HTTP clients
• Java generator hardened against code injection
• 🐛 Many other bug fixes and minor improvements

You can find the full changelog for this version in our GitHub release page.

Kubernetes 1.37 support (Garhwal)

This release adds support for Kubernetes v1.37.0 (Garhwal), keeping the client's model in sync with the latest Kubernetes API.

Along with the new APIs, several API versions that were removed upstream in Kubernetes v1.37.0 are no longer available in the client:

• certificates.k8s.io/v1alpha1/ClusterTrustBundle; use certificates.k8s.io/v1 or v1beta1
• networking.k8s.io/v1beta1/IPAddress and ServiceCIDR; use networking.k8s.io/v1
• storage.k8s.io/v1beta1/VolumeAttributesClass; use storage.k8s.io/v1
• scheduling.k8s.io/v1alpha2 (the entire API version, 28 types); use v1alpha3 or v1beta1

The canonical VolumeMount constructor signature has also changed to accommodate the new bindMountOptions field. If you build your resources with the fluent builders (new VolumeMountBuilder()...), you are unaffected; only direct calls to the canonical constructor need updating.

Gateway API 1.6 with TCPRoute and UDPRoute

The bundled Gateway API model has been updated from 1.5.1 to 1.6.1. As a result, v1.TCPRoute and v1.UDPRoute are now available, both having graduated from v1alpha2 upstream in Gateway API v1.6.0. The v1alpha2 types remain available, but upstream has deprecated them and plans to remove them in a future release, so new code should prefer the v1 types.

Note that v1.SessionPersistence no longer exposes idleTimeout, which was removed upstream in Gateway API v1.6.0. There is no runtime data loss: the class keeps its additionalProperties, so any YAML or JSON that still carries idleTimeout continues to deserialize and re-serialize intact.

WebSocket reliability on the Vert.x 5 and Jetty HTTP clients

A couple of important fixes land for WebSocket operations (exec, attach, portForward, and WebSocket-backed watches) on the optional kubernetes-httpclient-vertx-5 and kubernetes-httpclient-jetty modules.

On the Vert.x 5 client, derived clients (those produced internally, for example, when adapting to an OpenShiftClient or refreshing an OAuth token) were creating a brand-new WebSocket client with no configuration, discarding the cluster trust material and the configured frame and message size limits. Derived clients now reuse the original client's WebSocket transport, so TLS is verified against the configured cluster CA and the limits are honored.

Both the Vert.x 5 and Jetty clients now also route WebSocket connections through the configured proxy, instead of connecting straight to the API server and bypassing a mandated egress proxy. On the Vert.x 5 client, the configured connect timeout is now applied to WebSocket connections as well.

Note that the default bundled kubernetes-httpclient-vertx (Vert.x 4), OkHttp, and JDK modules were never affected, since they serve WebSockets from the same client they use for regular HTTP.

Java generator hardened against code injection

The java-generator now emits all schema-controlled values (enum values, the CRD group/version/names, property names, descriptions, and defaults) as fully escaped Java string literals, so a malicious CRD schema can no longer inject executable code into the generated sources. As a defense-in-depth measure, each generated class is also re-parsed and structurally validated before it is written, aborting generation on any residual mismatch.

Using this release

If your project is based on Maven, you just need to add the Fabric8 Kubernetes Client to your Maven dependencies:

<dependency>
  <groupId>io.fabric8</groupId>
  <artifactId>kubernetes-client</artifactId>
  <version>7.9.0</version>
</dependency>

If your project is based on Gradle, you just need to add the Fabric8 Kubernetes Client to your Gradle dependencies:

dependencies {
  api "io.fabric8:kubernetes-client:7.9.0"
}

Once your project is ready, you can create a new instance of the client to perform operations. In the following code snippet, I show you how to instantiate the client and retrieve a list of Pods:

try (KubernetesClient client = new KubernetesClientBuilder().build()) {
  client.pods().list().getItems().forEach(p -> System.out.println(p.getMetadata().getName()));
}

How can you help?

If you're interested in helping out and are a first-time contributor, check out the "good first issue" tag in the issue repository. We've tagged extremely easy issues so that you can get started contributing to Open Source.

We're also excited to read articles and posts mentioning our project and sharing the user experience. Giving a star to the project, and spreading the word in general, helps us reach more users and broaden the feedback. Feedback is the only way to improve.

Project Page | Issues | Discussions | Gitter | Stack Overflow