6.4.0 (2023-01-19)

[manusa]

Bugs

• Fix Upload InputStream To Pod with java.io.InterruptedIOException: interrupted (6.0.0-RC1) #4249: prevent the over-logging of errors after the websocket has been closed
• Fix facing classloader issue with gradle #4563: fallback to current class-loader when looking for HttpClient implementations
• Fix [Support] Fabric8 IO client creation is failing with below stacktrace #4650: allowing for comments at the end of certificate files
• Fix chore(deps): bump slf4j.version from 1.7.36 to 2.0.6 #4668: use acme.cert-manager.io ApiGroup for Orders and Challenges
• Fix LocalPortForward#close() returns before it is properly closed. #4726: prevent the over-logging of errors after the websocket has been closed
• Fix Ensure websockets and http responses are closed if the future is canceled #4729: ensuring CompletableFuture cancel will close / cancel the underlying resource
• Fix OpenShift s2i binary builds seem broken in 6.3 #4735: StandardHttpClient sends Expect 100-continue header value

Improvements

• Fix [java-generator] make the Maven plugin(and CLI?) able to fetch CRDs from URLs #4622: Java Generator Maven Plugin can use CRDs from remote URLs
• Fix run complains of having no name, when it is provided #4633: provided inline access to all RunConfig builder methods via run().withNewRunConfig()
• Fix Cannot run and attach a new pod that needs standard input #4637: all pod operations that require a ready / succeeded pod may use withReadyWaitTimeout, which supersedes withLogWaitTimeout.
• Fix public class GatewayClass implements Namespaced interface， but the scope of GatewayClass crd is Cluster #4654: Fix GatewayClass to not implement Namespaced interface
• Fix Set resourceVersion=0 for GET/LIST calls by default #4670: the initial informer listing will use a resourceVersion of 0 to utilize the watch cache if possible. This means that the initial cache state when the informer is returned, or the start future is completed, may not be as fresh as the previous behavior which forced the latest version. It will of course become more consistent as the watch will already have been established.
• Fix [java-generator] Overridable package name #4694: [java-generator] Option to override the package name of the generated code.
• Fix OkHttpClient connection leak in OperationSupport / HttpResponse #4720: interceptors close any response body if the response is not a 2xx response.
• Fix feat: @KubernetesTest annotation can be used in base test classes #4734: @KubernetesTest annotation can be used in base test classes
• Fix feat: @KubernetesTest annotation can be used in base test classes #4734: @KubernetesTest creates an ephemeral Namespace optionally (can opt-out)

New Features

• Fix Move to Vert.x HTTP Client #2764: Vert.x HttpClient implementation

Note: Breaking changes

• Fix Static deserialization issues #3972: deprecated Parameterizable and methods on Serialization accepting parameters - that was only needed as a workaround for non-string parameters. You should instead include those parameter values in the map passed to processLocally.
• Fix Static deserialization issues #3972: OpenShiftClient.load will no longer implicitly process templates. Use OpenShiftClient.templates().load instead.
• Fix Static deserialization issues #3972: WARNING: future client versions will not provide the static yaml and json ObjectMappersSerialization.
• Fix Client.resource(resource).get() does not return latest resource #4574: fromServer has been deprecated - it no longer needs to be called. All get() operations will fetch the resource(s) from the api server. If you need the context item that was passed in from a resource, load, or resourceList methods, use the item or items method.
• Fix run complains of having no name, when it is provided #4633: client.run().withRunConfig was deprecated. Use withNewRunConfig instead.
• Fix Seemingly indefinite wait at a get operation #4663: Config.maxConcurrentRequests and Config.maxConcurrentRequestsPerHost will no longer be used. Instead they will default to unlimited for all clients. Due to the ability of the fabric8 client to start long running requests (either websocket or regular http) and how this is treated by the underlying clients you can easily exhaust these values and enter a state where the client is unresponsive without any additional information on what is occurring.
• Fix [java-generator] Fix encoding for empty strings in enums #4769: java-generator Fix encoding of empty strings as valid enums

Full Changelog: v6.3.1...v6.4.0

---

This discussion was created from the release 6.4.0 (2023-01-19).