Bump io.fabric8:kubernetes-client from 6.5.1 to 6.7.2 in /modules/k3s

[dependabot]

Bumps io.fabric8:kubernetes-client from 6.5.1 to 6.7.2.

Release notes

Sourced from io.fabric8:kubernetes-client's releases.

6.7.2 (2023-06-15)

Bugs

• Fix #4225: Enum fields written in generated crd yaml
• Fix #5194: prevented NPEs due to timing issues with KubernetesClient.visitResources
• Fix #5214: null values are omitted by default, which means custom resources by in large won't need JsonIncludes annotations. The only time that is required is when null is to be preserved via @​JsonInclude(value = Include.ALWAYS) on the relevant field.
• Fix #5218: No export for io.fabric8.tekton.triggers.internal.knative.pkg.apis.duck.v1beta1 in tekton v1beta1 triggers model
• Fix #5224: Ensuring jetty sets the User-Agent header
• Fix #5229: Correcting the timeout units and behavior of withReadyWaitTimeout
• Fix #5235: Vert.x doesn't need to track derived HttpClients - prevents leakage
• Fix #5236: using scale v1beta1 compatible logic for DeploymentConfig
• Fix #5238: Preserve folder structure again in PodUpload.upload()
• Fix #5250: HttpLoggingInterceptor uses response body ByteBuffer copy

New Contributors

• @​leoandrea7 made their first contribution in fabric8io/kubernetes-client#4230

Full Changelog: fabric8io/kubernetes-client@v6.7.1...v6.7.2

6.7.1(2023-06-06)

Bugs

• Fix #5200: KubernetesSerialization.registerKubernetesResource(Class) reuses KubernetesDeserializer.Mapping.addMapping which is better supported when manually registering KubernetesResource classes
• Fix #5202: OkHttp needs to default to unlimited read timeout so that log watches and http watches do not time out

Full Changelog: fabric8io/kubernetes-client@v6.7.0...v6.7.1

6.7.0 (2023-06-01)

Bugs

• Fix #5117: corrected the trace httpclient logging of large response bodies
• Fix #5125: TLS 1.3 only should be supported
• Fix #5126: fallback to changeit only if null/empty does not work
• Fix #5145: [java-generator] handle additionalProperties: true emitting a field of type AnyType
• Fix #5152: preventing JDK WebSocket errors from terminating watches and improving watch termination and its logging
• Fix #5164: [java-generator] handle more special characters in field names

Improvements

• Fix #1335: HttpClient Factory additionalConfig consistently applied for all client types

Dependency Upgrade

• Fix #4989: Upgrade Tekton Model to v0.47.0
• Fix #5107: The Camel-k extension has been deprecated in favor of the official release of the generated one

New Features

• Fix #4184: Add utility methods for creating ConfigMap from files/directories in KubernetesResourceUtil
• Fix #4829: Gradle Plugin for Java Generation from CRD
• Fix #5086: Allow for supporting socks proxies via proxy urls with the socks4 or socks5 protocol. Note that the JDK client does not support socks, and the Jetty client does not support socks5

Note: Breaking changes

• Fix #4911: Config/RequestConfig.scaleTimeout has been deprecated along with Scalable.scale(count, wait) and DeployableScalableResource.deployLatest(wait). withTimeout may be called before the operation to control the timeout.
• Fix #4911: Config/RequestConfig.websocketTimeout has been removed. Config/RequestConfig.requestTimeout will be used for websocket connection timeouts.
• Fix #4911: HttpClient api/building changes - writeTimeout has been removed, readTimeout has moved to the HttpRequest

... (truncated)

Changelog

Sourced from io.fabric8:kubernetes-client's changelog.

6.7.2 (2023-06-15)

Bugs

• Fix #4225: Enum fields written in generated crd yaml
• Fix #5194: prevented NPEs due to timing issues with KubernetesClient.visitResources
• Fix #5214: null values are omitted by default, which means custom resources by in large won't need JsonIncludes annotations. The only time that is required is when null is to be preserved via @​JsonInclude(value = Include.ALWAYS) on the relevant field.
• Fix #5218: No export for io.fabric8.tekton.triggers.internal.knative.pkg.apis.duck.v1beta1 in tekton v1beta1 triggers model
• Fix #5224: Ensuring jetty sets the User-Agent header
• Fix #5229: Correcting the timeout units and behavior of withReadyWaitTimeout
• Fix #5235: Vert.x doesn't need to track derived HttpClients - prevents leakage
• Fix #5236: using scale v1beta1 compatible logic for DeploymentConfig
• Fix #5238: Preserve folder structure again in PodUpload.upload()
• Fix #5250: HttpLoggingInterceptor uses response body ByteBuffer copy

6.7.1(2023-06-06)

Bugs

• Fix #5200: KubernetesSerialization.registerKubernetesResource(Class) reuses KubernetesDeserializer.Mapping.addMapping which is better supported when manually registering KubernetesResource classes
• Fix #5202: OkHttp needs to default to unlimited read timeout so that log watches and http watches do not time out

6.7.0 (2023-06-01)

Bugs

• Fix #5117: corrected the trace httpclient logging of large response bodies
• Fix #5125: TLS 1.3 only should be supported
• Fix #5126: fallback to changeit only if null/empty does not work
• Fix #5145: [java-generator] handle additionalProperties: true emitting a field of type AnyType
• Fix #5152: preventing JDK WebSocket errors from terminating watches and improving watch termination and its logging
• Fix #5164: [java-generator] handle more special characters in field names

Improvements

• Fix #1335: HttpClient Factory additionalConfig consistently applied for all client types

Dependency Upgrade

• Fix #4989: Upgrade Tekton Model to v0.47.0
• Fix #5107: The Camel-k extension has been deprecated in favor of the official release of the generated one

New Features

• Fix #4184: Add utility methods for creating ConfigMap from files/directories in KubernetesResourceUtil
• Fix #4829: Gradle Plugin for Java Generation from CRD
• Fix #5086: Allow for supporting socks proxies via proxy urls with the socks4 or socks5 protocol. Note that the JDK client does not support socks, and the Jetty client does not support socks5

Note: Breaking changes

• Fix #4911: Config/RequestConfig.scaleTimeout has been deprecated along with Scalable.scale(count, wait) and DeployableScalableResource.deployLatest(wait). withTimeout may be called before the operation to control the timeout.
• Fix #4911: Config/RequestConfig.websocketTimeout has been removed. Config/RequestConfig.requestTimeout will be used for websocket connection timeouts.
• Fix #4911: HttpClient api/building changes - writeTimeout has been removed, readTimeout has moved to the HttpRequest
• Fix #4662: removed deprecated classes/methods: ReflectUtils, ReplaceValueStream, ParameterNamespaceListVisitFromServerGetDeleteRecreateWaitApplicable, ResourceCompare, and Serialization methods taking parameters
• Fix #4662: deprecated serialization static logic: several IOHelpers methods, Serialization methods, such as access to the static jsonMapper. Please use KubernetesSerialization methods instead.
• Fix #4662: deprecated Helper.getAnnotationValue, use HasMetadata methods instead.
• Fix #5125: support for TLSv1.3 is now enabled by default

... (truncated)

Commits

• 3d56a27 [RELEASE] Updated project version to v6.7.2
• 6899cb4 test: PodIT don't rely on PodResource.file.read to verify the contents of the...
• 63bcd03 fix: HttpLoggingInterceptor uses response body ByteBuffer copy
• 6170b04 preventing conflicts with dc update
• 72fe5ae fix #5229: allowing for other exits from the readiness check
• 2641818 fix #5194: showing the groups that were visited
• 3e5ae25 fix #5194: prevent NPEs when the APIResourceList is missing
• 8573932 fix #5194: deflaking ScaleIT by ensuring api metadata lookup succeeds
• 7c71222 switching to a relative root for tar entries
• b9e58cf test: PodIT uploadDir test checks for nested directories
• 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)