Bump kubernetes-client-bom from 5.12.2 to 6.5.1

[dependabot]

Bumps kubernetes-client-bom from 5.12.2 to 6.5.1.

Release notes

Sourced from kubernetes-client-bom's releases.

6.5.1 (2023-03-20)

Bugs

• Fix #4960: NPE in OpenIDConnectionUtils if idp-certificate-authority-data absent in auth-provider config
• Fix #4970: OpenShiftOAuthInterceptor should not refresh on 403 response code
• Fix #4981: Prevent StackOverflowError in Vert.x HttpClient caused by fast InputStream buffer extraction

6.5.0 (2023-03-10)

Bugs

• Fix #4723: (java-generator) Fix a race in the use of JavaParser hitting large CRDs
• Fix #4784: json-schema draft-05 is a (404). Updating to draft-07 (http://json-schema.org/draft-07/schema#)
• Fix #4791: handle the NullPointerException in Thread.currentThread().getContextClassLoader()
• Fix #4794: improving the semantics of manually calling informer stop
• Fix #4797: OkHttpClientFactory.additionalConfig can be used to override the default OkHttp Dispatcher
• Fix #4798: fix leader election release on cancel
• Fix #4803: Windows .kube/config file with spaces in command can be deserialized
• Fix #4815: (java-generator) create target download directory if it doesn't exist
• Fix #4818: (java-generator) Escape */ in generated JavaDocs
• Fix #4823: (java-generator) handle special characters in field names
• Fix #4832: NO_PROXY can match cidr with bit suffix <10
• Fix #4846: allowed for pod read / copy operations to distinguish when the target doesn't exist
• Fix #4851: adding buffer cloning to ensure buffers cannot be modified after sending
• Fix #4885: addresses a potential hang in the jdk client with exec stream reading
• Fix #4888: narrowing where the 0 initial list resourceVersion is used for informers - in particular if a limit is set or initialState is used, then we should not use 0. Additionally for the informOnCondition / wait methods we'll also not use 0 - it's not expected that the user should test any state prior to the latest.
• Fix #4891: address vertx not completely reading exec streams
• Fix #4899: BuildConfigs.instantiateBinary().fromFile() does not time out
• Fix #4908: using the response headers in the vertx response
• Fix #4910: addressing inconsistent behavior with pod exec operations
• Fix #4923: addressing inconsistent behavior with pod exec operations
• Fix #4928: allows non-okhttp clients to handle invalid status
• Fix #4931: using coarse grain locking for all mock server operations
• Fix #4947: typo in HttpClient.Factory scoring system logic
• Fix #4954: disabling expect continue support by default in the jdk client

Improvements

• Fix #4675: adding a fully client side timeout for informer watches
• Fix #3805: DeletionTimestamp and Finalizer support in Mock server.
• Fix #4638: adding a way to set the full object meta on a leadership election lock, this can be used to set owner references
• Fix #4644: generate CRDs in parallel and optimize code
• Fix #4659: added a generic support(apiversion, kind) method in addition to the class based check
• Fix #4724: Private configuration classes cause trouble with Java native (reflection)
• Fix #4739: honor optimistic concurrency control semantics in the mock server for PUT and PATCH requests.
• Fix #4747: migrate to SnakeYAML Engine
• Fix #4788: moved retry logic into the standard client so that it applies to all requests, including websockets
• Fix #4795: don't print warning message when service account token property is unset
• Fix #4800: (java-generator) Reflect the scope field when implementing the Namespaced interface
• Fix #4853: adding a wait on the pod for log operations
• Fix #4848: Vert.x async DNS resolver is disabled
• Fix #4863: default HttpClient retry logic to 100ms interval
• Fix #4863: default HttpClient retry logic to 10 attempts
• Fix #4865: (java-generator) performance improvements

... (truncated)

Changelog

Sourced from kubernetes-client-bom's changelog.

6.5.1 (2023-03-20)

Bugs

• Fix #4960: NPE in OpenIDConnectionUtils if idp-certificate-authority-data absent in auth-provider config
• Fix #4970: OpenShiftOAuthInterceptor should not refresh on 403 response code
• Fix #4981: Prevent StackOverflowError in Vert.x HttpClient caused by fast InputStream buffer extraction

6.5.0 (2023-03-10)

Bugs

• Fix #4723: (java-generator) Fix a race in the use of JavaParser hitting large CRDs
• Fix #4784: json-schema draft-05 is a (404). Updating to draft-07 (http://json-schema.org/draft-07/schema#)
• Fix #4791: handle the NullPointerException in Thread.currentThread().getContextClassLoader()
• Fix #4794: improving the semantics of manually calling informer stop
• Fix #4797: OkHttpClientFactory.additionalConfig can be used to override the default OkHttp Dispatcher
• Fix #4798: fix leader election release on cancel
• Fix #4803: Windows .kube/config file with spaces in command can be deserialized
• Fix #4815: (java-generator) create target download directory if it doesn't exist
• Fix #4818: (java-generator) Escape */ in generated JavaDocs
• Fix #4823: (java-generator) handle special characters in field names
• Fix #4832: NO_PROXY can match cidr with bit suffix <10
• Fix #4846: allowed for pod read / copy operations to distinguish when the target doesn't exist
• Fix #4851: adding buffer cloning to ensure buffers cannot be modified after sending
• Fix #4885: addresses a potential hang in the jdk client with exec stream reading
• Fix #4888: narrowing where the 0 initial list resourceVersion is used for informers - in particular if a limit is set or initialState is used, then we should not use 0. Additionally for the informOnCondition / wait methods we'll also not use 0 - it's not expected that the user should test any state prior to the latest.
• Fix #4891: address vertx not completely reading exec streams
• Fix #4899: BuildConfigs.instantiateBinary().fromFile() does not time out
• Fix #4908: using the response headers in the vertx response
• Fix #4910: addressing inconsistent behavior with pod exec operations
• Fix #4923: addressing inconsistent behavior with pod exec operations
• Fix #4928: allows non-okhttp clients to handle invalid status
• Fix #4931: using coarse grain locking for all mock server operations
• Fix #4947: typo in HttpClient.Factory scoring system logic
• Fix #4954: disabling expect continue support by default in the jdk client

Improvements

• Fix #4675: adding a fully client side timeout for informer watches
• Fix #3805: DeletionTimestamp and Finalizer support in Mock server.
• Fix #4638: adding a way to set the full object meta on a leadership election lock, this can be used to set owner references
• Fix #4644: generate CRDs in parallel and optimize code
• Fix #4659: added a generic support(apiversion, kind) method in addition to the class based check
• Fix #4724: Private configuration classes cause trouble with Java native (reflection)
• Fix #4739: honor optimistic concurrency control semantics in the mock server for PUT and PATCH requests.
• Fix #4747: migrate to SnakeYAML Engine
• Fix #4788: moved retry logic into the standard client so that it applies to all requests, including websockets
• Fix #4795: don't print warning message when service account token property is unset
• Fix #4800: (java-generator) Reflect the scope field when implementing the Namespaced interface
• Fix #4853: adding a wait on the pod for log operations
• Fix #4848: Vert.x async DNS resolver is disabled
• Fix #4863: default HttpClient retry logic to 100ms interval

... (truncated)

Commits

• b8e927b [RELEASE] Updated project version to v6.5.1
• 1160881 chore(deps): bump maven-core from 3.9.0 to 3.9.1
• 6bbe2e2 chore: add changelog entry for Vert.x stackoverflow fix
• be4aa07 The implementation of the InputStream to ReadStream adapter can sometimes do ...
• bf992cd fix (kubernetes-client-api) : Default to cluster cert data if `idp-certificat...
• 700dab3 fix (openshift-client) : OpenShiftOAuthInterceptor should not refresh on `403...
• 3710714 chore(deps): bump really-executable-jar-maven-plugin from 2.1.0 to 2.1.1
• ccc8aa1 chore(deps): bump maven.surefire.plugin.version from 3.0.0-M9 to 3.0.0
• ddfab72 [RELEASE] Prepare for next development iteration
• 2e2caaf [RELEASE] Updated project version to v6.5.0
• Additional commits viewable in compare view

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)