Fix #4249: prevent the over-logging of errors after the websocket has been closed
Fix #4563: fallback to current class-loader when looking for HttpClient implementations
Fix #4650: allowing for comments at the end of certificate files
Fix #4668: use acme.cert-manager.io ApiGroup for Orders and Challenges
Fix #4726: prevent the over-logging of errors after the websocket has been closed
Fix #4729: ensuring CompletableFuture cancel will close / cancel the underlying resource
Fix #4735: StandardHttpClient sends Expect 100-continue header value
Improvements
Fix #4622: Java Generator Maven Plugin can use CRDs from remote URLs
Fix #4633: provided inline access to all RunConfig builder methods via run().withNewRunConfig()
Fix #4637: all pod operations that require a ready / succeeded pod may use withReadyWaitTimeout, which supersedes withLogWaitTimeout.
Fix #4654: Fix GatewayClass to not implement Namespaced interface
Fix #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 #4694: [java-generator] Option to override the package name of the generated code.
Fix #4720: interceptors close any response body if the response is not a 2xx response.
Fix #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 #3972: OpenShiftClient.load will no longer implicitly process templates. Use OpenShiftClient.templates().load instead.
Fix #3972: WARNING: future client versions will not provide the static yaml and json ObjectMappersSerialization.
Fix #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 #4633: client.run().withRunConfig was deprecated. Use withNewRunConfig instead.
Fix #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 #4769: java-generator Fix encoding of empty strings as valid enums
Fix #4811: HttpClient.Factory instances can be prioritized
6.4.0 (2023-01-19)
Bugs
Fix #4249: prevent the over-logging of errors after the websocket has been closed
Fix #4563: fallback to current class-loader when looking for HttpClient implementations
Fix #4650: allowing for comments at the end of certificate files
Fix #4668: use acme.cert-manager.io ApiGroup for Orders and Challenges
Fix #4726: prevent the over-logging of errors after the websocket has been closed
Fix #4729: ensuring CompletableFuture cancel will close / cancel the underlying resource
Fix #4735: StandardHttpClient sends Expect 100-continue header value
Improvements
Fix #4622: Java Generator Maven Plugin can use CRDs from remote URLs
Fix #4633: provided inline access to all RunConfig builder methods via run().withNewRunConfig()
Fix #4637: all pod operations that require a ready / succeeded pod may use withReadyWaitTimeout, which supersedes withLogWaitTimeout.
Fix #4654: Fix GatewayClass to not implement Namespaced interface
Fix #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 #4694: [java-generator] Option to override the package name of the generated code.
Fix #4698: changes were made to improve authentication logic. If a username and password are specified and you are using a base KuberentesClient, then that will always be used as a basic auth header value. If a username and password are specified and you are using an OpenShiftClient, then a token will still be used if present, but upon an auth failure the username and password will be used to obtain a fresh token. If a new token is obtained it will be saved in the kubeconfig if one were used to create the Config.
Fix #4720: interceptors close any response body if the response is not a 2xx response.
Fix #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 #3972: OpenShiftClient.load will no longer implicitly process templates. Use OpenShiftClient.templates().load instead.
Fix #3972: WARNING: future client versions will not provide the static yaml and json ObjectMappers on Serialization.
Fix #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 #4633: client.run().withRunConfig was deprecated. Use withNewRunConfig instead.
Fix #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 #4769: java-generator Fix encoding of empty strings as valid enums
6.3.1 (2022-12-15)
Bugs
Fix #4666: fixed okhttp calls not explicitly closing
Fix #4673: fixes a regression in sharing the OpenShiftOAuthInterceptor token
Fix #4677: java-generator Fix default encoding of enums
6.3.0 (2022-12-12)
... (truncated)
Commits
8d70908 [RELEASE] Updated project version to v6.4.1
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps io.fabric8:kubernetes-client from 5.12.4 to 6.4.1.
Release notes
Sourced from io.fabric8:kubernetes-client's releases.
... (truncated)
Changelog
Sourced from io.fabric8:kubernetes-client's changelog.
... (truncated)
Commits
8d70908[RELEASE] Updated project version to v6.4.1fd9a5d2chore: add missing 6.4.1 changelog entries07014fbchore: add missing changelog entry for #47959f00e1fDon't print warning message when service account token property is unset5ffca33fix: HttpClient.Factory instances can be prioritized55357e1refactor: VertxHttpClientBuilder is publiccb3be92[RELEASE] Updated project version to v6.4.00cd1d26chore: sanitize changelog before next release04264e0[java-generator] Update documentationbbb626aDoc: Cheatsheet ingress should use network v1 apiDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)