chore(deps): update dependency kubernetes.core to v6.6.0 #18

Open
renovate-bot wants to merge 1 commit from renovate/kubernetes.core-6.x into main
Member

This PR contains the following updates:

Package Type Update Change
kubernetes.core galaxy-collection minor 6.1.0 → 6.6.0

Release Notes

ansible-collections/kubernetes.core (kubernetes.core)

v6.6.0

Compare Source

======

Minor Changes

  • Remove the remaining ansible.module_utils.six import to avoid deprecation warnings, replacing it with the Python standard library equivalent (#​1197).
  • helm - Add wait_for_jobs option to wait for all Jobs to complete before marking a Helm release as successful. Requires Helm >= 3.5.0 (#​1140).
  • helm - add the cleanup_on_fail option, mapping to the --cleanup-on-fail flag, to allow deletion of new resources created during a failed upgrade. It complements atomic and can be combined with it, but cannot be used with replace, since that deploys through helm install which does not accept the flag (#​1206).
  • helm - warn when reuse_values or reset_then_reuse_values is requested in a combination helm ignores, which happens by default because reset_values defaults to true, and whenever either is combined with replace. The option descriptions and the examples now state that reset_values has to be set to false for either option to take effect (#​1230).
  • k8s lookup - warn when ENABLE_TURBO_MODE is set but the cloud.common collection is not installed, instead of silently falling back to the standard lookup base (#​1242).
  • k8s_cp - Add the copy_timeout option (default 300 seconds) bounding how long the module will spend streaming an archive to a pod and waiting for the remote tar to finish, so that a stalled copy fails instead of hanging indefinitely (#​1217).
  • k8s_cp - Stream the tar archive to the pod chunk by chunk instead of building the whole archive in memory first, which cuts peak memory use when copying large files (#​1217).
  • k8s_cp - When copying to a pod, the module now also uses /bin/sh and head in the container, when present, to confirm the copy completed. Containers without them keep the previous behaviour and get a warning that completion could not be verified (#​1217).
  • k8s_info - Support for metadata-only fetches in k8s_info module (#​1030)
  • meta - Add helm_plugin and helm_plugin_info to the helm action group, and k8s_taint to the k8s action group, so that module_defaults set on those groups applies to them (#​1216).
  • use collections.abc instead of deprecated ansible.module_utils.common._collections_compat (#​1057).
  • waiter - Add job_complete predicate to support waiting for Job resources to reach Complete or Failed condition (#​1201).

Deprecated Features

  • Ansible Turbo mode (ENABLE_TURBO_MODE) has been deprecated and will be removed in release 8.0.0, as it depends on the cloud.common collection, which is being retired (#​1242).
  • helm - the status.values return value has been deprecated and will be removed in version 8.0.0. Use status.release_values instead (#​1239).
  • helm - the wait_timeout parameter has been deprecated and will be removed in version 7.0.0. Use timeout instead (#​1239).
  • helm_info - the status.values return value has been deprecated and will be removed in version 8.0.0. Use status.release_values instead (#​1239).
  • k8s_exec - the return_code return value has been deprecated and will be removed in version 7.0.0. Use rc instead (#​1239).
  • k8s_service - the merge_type=json option has been deprecated and will be removed in version 7.0.0. Use kubernetes.core.k8s_json_patch module instead (#​1239).

Bugfixes

  • Ansible Turbo mode - ignore ENABLE_TURBO_MODE on ansible-core 2.19.0 and later, where the cloud.common collection is not supported, and fall back to the standard AnsibleModule instead of failing with byte indices must be integers or slices, not str (#​1242).
  • helm - do not pass the upgrade-only --reuse-values and --reset-then-reuse-values flags to helm install, which rejected them with unknown flag whenever reuse_values or reset_then_reuse_values was combined with replace (#​1230).
  • helm - fix the reuse_values example, which set only reuse_values=true. reset_values defaults to true and helm ignores --reuse-values whenever --reset-values is passed, so following the example reset the release values instead of reusing them (#​1230).
  • helm - skip Helm's OCI registry progress messages when parsing the output of helm show chart. As of Helm 4.2.1 these are printed to stdout instead of stderr (helm/helm#32056), which made installing a chart from an OCI registry fail with a YAML scanner error when the chart version contained a + (#​1223).
  • helm_repository - normalize both sides of the repository URL comparison, so that a repository already registered with a trailing slash is recognized as matching instead of failing with Repository already have a repository named <name> (#​1236).
  • helm_template - strip Helm's OCI registry progress messages from the returned stdout, which is documented to contain only the rendered templates (#​1223).
  • k8s lookup - ignore ENABLE_TURBO_MODE on ansible-core 2.19.0 and later, where the cloud.common collection is not supported. Fall back to the standard LookupBase instead of failing with a traceback (#​1253).
  • k8s_cp - Fix silent truncation when copying to a pod. The module closed the exec connection immediately after writing the last chunk of the tar archive, which killed the remote tar before it had finished extracting, and never checked the process exit status, so a partial copy was reported as a success. The archive is now bounded with head -c so tar gets a clean EOF and exits on its own, and the module waits for that exit and fails on a non-zero status (#​1217).
  • k8s_info - Handle empty template output gracefully by returning changed=false instead of failing when Jinja2 template renders to an empty string (#​1042).

v6.5.0

Compare Source

======

Release Summary

This release implements minor changes and bug fixes such as a new remove value to the behavior option of the kubeconfig module, allowing entries to be deleted from the kubeconfig file by name, as well as Helm v4 compatibility across the Helm modules.

Minor Changes

  • helm - add the server_side and force_conflicts options to control Helm v4 server-side apply when installing or upgrading a release (#​1164).
  • helm_plugin - add --keyring argument to allow changing the keyring default location. The option is only accepted with state=present (the helm plugin install subcommand), as that is the only implemented subcommand that supports --keyring (#​1150).
  • helm_registry_auth - document that, as of Helm 4.2.1, registry success messages such as Login Succeeded are printed to stdout instead of stderr (#​1147).
  • kubeconfig - add remove value to the behavior option, allowing entries to be deleted from the kubeconfig file by name (#​1123).

Bugfixes

  • ee - added meta/execution-environment.yml to decouple ansible-builder EE builds from the openshift-clients system dependency declared in bindep.txt, which is not available in standard UBI repositories and caused builds to fail with No package matches 'openshift-clients' (#​1141).
  • helm - use --server-side=false --force-replace instead of the deprecated/removed --force flag when force=true is used with Helm v4, preserving the Helm v3 client-side replacement behaviour and avoiding the server-side apply conflict (#​1164).
  • helm - use the --rollback-on-failure flag instead of the deprecated/removed --atomic flag when atomic=true is used with Helm v4 (#​1144).
  • helm_repository - correct handling of repository URLs with trailing slashes (#​1121).
  • k8s_drain - Fix logic for handling pods with local storage to correctly check for empty_dir volumes in replicated pods and pods managed by DaemonSets (#​1095).

New Modules

  • kubeconfig - Generate, update, and optionally write Kubernetes kubeconfig files

v6.4.0

Compare Source

======

Release Summary

This release adds Helm v4 compatibility across the Helm modules and improves k8s_drain with check mode. When you explicitly allow evicting unmanaged pods, pods with local storage, or pods managed by a DaemonSet, those cases are reported as informational output instead of module warnings.

Minor Changes

  • helm_info - Ensure compatibility with Helm v4 (#​1038).
  • helm_plugin - Ensure compatibility with Helm v4 (#​1038).
  • helm_plugin_info - Ensure compatibility with Helm v4 (#​1038).
  • helm_pull - Ensure compatibility with Helm v4 (#​1038).
  • helm_registry_auth - Ensure compatibility with Helm v4 (#​1038).
  • helm_registry_auth - add new option plain_http to allow insecure http connection when running helm registry login (#​1090).
  • helm_repository - Ensure compatibility with Helm v4 (#​1038).
  • k8s_drain - Add support for check_mode (#​1086).
  • k8s_drain - Convert module warnings into informational displays when users explicitly request the deletion of unmanaged pods, pods with local storage, or those managed by a DaemonSet (#​1037).

Bugfixes

  • Helm - Allow taking ownership of existing Kubernetes resources on the first installation of a Helm release. Previously, the take_ownership parameter was always disabled during the initial install, preventing resource adoption (#​1034).

v6.3.0

Compare Source

======

Release Summary

This release includes bugfixes such as implementing idempotency for the helm_pull module as well as a security update for selectively redacting sensitive information from kubeconfig.

Minor Changes

  • Remove deprecated import from ansible.module_utils._text (#​1053).
  • helm - add release_values key to status return value that can be accessed using Jinja2 dot notation (#​1056).
  • helm_info - add release_values key to status return value that can be accessed using Jinja2 dot notation (#​1056).

Deprecated Features

  • helm - the status.values return value has been deprecated and will be removed in a release after 2027-01-08. Use status.release_values instead (#​1056).
  • helm_info - the status.values return value has been deprecated and will be removed in a release after 2027-01-08. Use status.release_values instead (#​1056).

Security Fixes

  • Selectively redact sensitive info from kubeconfig instead of applying blanket no_log=True (#​1014).

Bugfixes

  • Add idempotency for helm_pull module (#​1055).
  • Fixed a bug where setting K8S_AUTH_VERIFY_SSL=true (or any string value) caused the value to be treated as a separate kubectl command argument. (#​1049).
  • Limit supported versions of Helm to <4.0.0 (#​1039).
  • Replace passing warnings to exit_json with AnsibleModule.warn in the k8s_drain, k8s_rollback.py and k8s_scale.py modules as it deprecated in ansible-core>=2.19.0 and will be removed in ansible-core>=2.23.0 (#​1033).
  • k8s - Fix return block from the module documentation (#​1056).
  • meta - Add k8s_cluster_info, k8s_json_patch and k8s_rollback to k8s action group (#​992).

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [kubernetes.core](https://github.com/ansible-collections/kubernetes.core) | galaxy-collection | minor | `6.1.0` → `6.6.0` | --- ### Release Notes <details> <summary>ansible-collections/kubernetes.core (kubernetes.core)</summary> ### [`v6.6.0`](https://github.com/ansible-collections/kubernetes.core/blob/HEAD/CHANGELOG.rst#v660) [Compare Source](https://github.com/ansible-collections/kubernetes.core/compare/6.5.0...6.6.0) \====== ## Minor Changes - Remove the remaining `ansible.module_utils.six` import to avoid deprecation warnings, replacing it with the Python standard library equivalent ([#&#8203;1197](https://github.com/ansible-collections/kubernetes.core/pull/1197)). - helm - Add `wait_for_jobs` option to wait for all Jobs to complete before marking a Helm release as successful. Requires Helm >= 3.5.0 ([#&#8203;1140](https://github.com/ansible-collections/kubernetes.core/pull/1140)). - helm - add the `cleanup_on_fail` option, mapping to the `--cleanup-on-fail` flag, to allow deletion of new resources created during a failed upgrade. It complements `atomic` and can be combined with it, but cannot be used with `replace`, since that deploys through `helm install` which does not accept the flag ([#&#8203;1206](https://github.com/ansible-collections/kubernetes.core/pull/1206)). - helm - warn when `reuse_values` or `reset_then_reuse_values` is requested in a combination helm ignores, which happens by default because `reset_values` defaults to `true`, and whenever either is combined with `replace`. The option descriptions and the examples now state that `reset_values` has to be set to `false` for either option to take effect ([#&#8203;1230](https://github.com/ansible-collections/kubernetes.core/pull/1230)). - k8s lookup - warn when `ENABLE_TURBO_MODE` is set but the `cloud.common` collection is not installed, instead of silently falling back to the standard lookup base ([#&#8203;1242](https://github.com/ansible-collections/kubernetes.core/pull/1242)). - k8s\_cp - Add the `copy_timeout` option (default 300 seconds) bounding how long the module will spend streaming an archive to a pod and waiting for the remote `tar` to finish, so that a stalled copy fails instead of hanging indefinitely ([#&#8203;1217](https://github.com/ansible-collections/kubernetes.core/pull/1217)). - k8s\_cp - Stream the tar archive to the pod chunk by chunk instead of building the whole archive in memory first, which cuts peak memory use when copying large files ([#&#8203;1217](https://github.com/ansible-collections/kubernetes.core/pull/1217)). - k8s\_cp - When copying to a pod, the module now also uses `/bin/sh` and `head` in the container, when present, to confirm the copy completed. Containers without them keep the previous behaviour and get a warning that completion could not be verified ([#&#8203;1217](https://github.com/ansible-collections/kubernetes.core/pull/1217)). - k8s\_info - Support for metadata-only fetches in k8s\_info module ([#&#8203;1030](https://github.com/ansible-collections/kubernetes.core/pull/1030)) - meta - Add `helm_plugin` and `helm_plugin_info` to the `helm` action group, and `k8s_taint` to the `k8s` action group, so that `module_defaults` set on those groups applies to them ([#&#8203;1216](https://github.com/ansible-collections/kubernetes.core/pull/1216)). - use `collections.abc` instead of deprecated `ansible.module_utils.common._collections_compat` ([#&#8203;1057](https://github.com/ansible-collections/kubernetes.core/pull/1057)). - waiter - Add `job_complete` predicate to support waiting for Job resources to reach `Complete` or `Failed` condition ([#&#8203;1201](https://github.com/ansible-collections/kubernetes.core/issues/1201)). ## Deprecated Features - Ansible Turbo mode (`ENABLE_TURBO_MODE`) has been deprecated and will be removed in release 8.0.0, as it depends on the `cloud.common` collection, which is being retired ([#&#8203;1242](https://github.com/ansible-collections/kubernetes.core/pull/1242)). - helm - the `status.values` return value has been deprecated and will be removed in version 8.0.0. Use `status.release_values` instead ([#&#8203;1239](https://github.com/ansible-collections/kubernetes.core/issues/1239)). - helm - the `wait_timeout` parameter has been deprecated and will be removed in version 7.0.0. Use `timeout` instead ([#&#8203;1239](https://github.com/ansible-collections/kubernetes.core/issues/1239)). - helm\_info - the `status.values` return value has been deprecated and will be removed in version 8.0.0. Use `status.release_values` instead ([#&#8203;1239](https://github.com/ansible-collections/kubernetes.core/issues/1239)). - k8s\_exec - the `return_code` return value has been deprecated and will be removed in version 7.0.0. Use `rc` instead ([#&#8203;1239](https://github.com/ansible-collections/kubernetes.core/issues/1239)). - k8s\_service - the `merge_type=json` option has been deprecated and will be removed in version 7.0.0. Use `kubernetes.core.k8s_json_patch` module instead ([#&#8203;1239](https://github.com/ansible-collections/kubernetes.core/issues/1239)). ## Bugfixes - Ansible Turbo mode - ignore `ENABLE_TURBO_MODE` on ansible-core 2.19.0 and later, where the `cloud.common` collection is not supported, and fall back to the standard `AnsibleModule` instead of failing with `byte indices must be integers or slices, not str` ([#&#8203;1242](https://github.com/ansible-collections/kubernetes.core/pull/1242)). - helm - do not pass the upgrade-only `--reuse-values` and `--reset-then-reuse-values` flags to `helm install`, which rejected them with `unknown flag` whenever `reuse_values` or `reset_then_reuse_values` was combined with `replace` ([#&#8203;1230](https://github.com/ansible-collections/kubernetes.core/pull/1230)). - helm - fix the `reuse_values` example, which set only `reuse_values=true`. `reset_values` defaults to `true` and helm ignores `--reuse-values` whenever `--reset-values` is passed, so following the example reset the release values instead of reusing them ([#&#8203;1230](https://github.com/ansible-collections/kubernetes.core/pull/1230)). - helm - skip Helm's OCI registry progress messages when parsing the output of `helm show chart`. As of Helm 4.2.1 these are printed to stdout instead of stderr ([helm/helm#32056](https://github.com/helm/helm/pull/32056)), which made installing a chart from an OCI registry fail with a YAML scanner error when the chart version contained a `+` ([#&#8203;1223](https://github.com/ansible-collections/kubernetes.core/pull/1223)). - helm\_repository - normalize both sides of the repository URL comparison, so that a repository already registered with a trailing slash is recognized as matching instead of failing with `Repository already have a repository named <name>` ([#&#8203;1236](https://github.com/ansible-collections/kubernetes.core/pull/1236)). - helm\_template - strip Helm's OCI registry progress messages from the returned `stdout`, which is documented to contain only the rendered templates ([#&#8203;1223](https://github.com/ansible-collections/kubernetes.core/pull/1223)). - k8s lookup - ignore `ENABLE_TURBO_MODE` on ansible-core 2.19.0 and later, where the `cloud.common` collection is not supported. Fall back to the standard `LookupBase` instead of failing with a traceback ([#&#8203;1253](https://github.com/ansible-collections/kubernetes.core/pull/1253)). - k8s\_cp - Fix silent truncation when copying to a pod. The module closed the exec connection immediately after writing the last chunk of the tar archive, which killed the remote `tar` before it had finished extracting, and never checked the process exit status, so a partial copy was reported as a success. The archive is now bounded with `head -c` so `tar` gets a clean EOF and exits on its own, and the module waits for that exit and fails on a non-zero status ([#&#8203;1217](https://github.com/ansible-collections/kubernetes.core/pull/1217)). - k8s\_info - Handle empty template output gracefully by returning `changed=false` instead of failing when Jinja2 template renders to an empty string ([#&#8203;1042](https://github.com/ansible-collections/kubernetes.core/issues/1042)). ### [`v6.5.0`](https://github.com/ansible-collections/kubernetes.core/blob/HEAD/CHANGELOG.rst#v650) [Compare Source](https://github.com/ansible-collections/kubernetes.core/compare/6.4.0...6.5.0) \====== ## Release Summary This release implements minor changes and bug fixes such as a new `remove` value to the `behavior` option of the `kubeconfig` module, allowing entries to be deleted from the kubeconfig file by name, as well as Helm v4 compatibility across the Helm modules. ## Minor Changes - helm - add the `server_side` and `force_conflicts` options to control Helm v4 server-side apply when installing or upgrading a release ([#&#8203;1164](https://github.com/ansible-collections/kubernetes.core/pull/1164)). - helm\_plugin - add `--keyring` argument to allow changing the keyring default location. The option is only accepted with `state=present` (the `helm plugin install` subcommand), as that is the only implemented subcommand that supports `--keyring` ([#&#8203;1150](https://github.com/ansible-collections/kubernetes.core/pull/1150)). - helm\_registry\_auth - document that, as of Helm 4.2.1, registry success messages such as `Login Succeeded` are printed to stdout instead of stderr ([#&#8203;1147](https://github.com/ansible-collections/kubernetes.core/pull/1147)). - kubeconfig - add `remove` value to the `behavior` option, allowing entries to be deleted from the kubeconfig file by name ([#&#8203;1123](https://github.com/ansible-collections/kubernetes.core/pull/1123)). ## Bugfixes - ee - added `meta/execution-environment.yml` to decouple ansible-builder EE builds from the `openshift-clients` system dependency declared in `bindep.txt`, which is not available in standard UBI repositories and caused builds to fail with `No package matches 'openshift-clients'` ([#&#8203;1141](https://github.com/ansible-collections/kubernetes.core/issues/1141)). - helm - use `--server-side=false --force-replace` instead of the deprecated/removed `--force` flag when `force=true` is used with Helm v4, preserving the Helm v3 client-side replacement behaviour and avoiding the server-side apply conflict ([#&#8203;1164](https://github.com/ansible-collections/kubernetes.core/pull/1164)). - helm - use the `--rollback-on-failure` flag instead of the deprecated/removed `--atomic` flag when `atomic=true` is used with Helm v4 ([#&#8203;1144](https://github.com/ansible-collections/kubernetes.core/pull/1144)). - helm\_repository - correct handling of repository URLs with trailing slashes ([#&#8203;1121](https://github.com/ansible-collections/kubernetes.core/pull/1121)). - k8s\_drain - Fix logic for handling pods with local storage to correctly check for empty\_dir volumes in replicated pods and pods managed by DaemonSets ([#&#8203;1095](https://github.com/ansible-collections/kubernetes.core/pull/1095)). ## New Modules - kubeconfig - Generate, update, and optionally write Kubernetes kubeconfig files ### [`v6.4.0`](https://github.com/ansible-collections/kubernetes.core/blob/HEAD/CHANGELOG.rst#v640) [Compare Source](https://github.com/ansible-collections/kubernetes.core/compare/6.3.0...6.4.0) \====== ## Release Summary This release adds Helm v4 compatibility across the Helm modules and improves `k8s_drain` with check mode. When you explicitly allow evicting unmanaged pods, pods with local storage, or pods managed by a `DaemonSet`, those cases are reported as informational output instead of module warnings. ## Minor Changes - helm\_info - Ensure compatibility with Helm v4 ([#&#8203;1038](https://github.com/ansible-collections/kubernetes.core/issues/1038)). - helm\_plugin - Ensure compatibility with Helm v4 ([#&#8203;1038](https://github.com/ansible-collections/kubernetes.core/issues/1038)). - helm\_plugin\_info - Ensure compatibility with Helm v4 ([#&#8203;1038](https://github.com/ansible-collections/kubernetes.core/issues/1038)). - helm\_pull - Ensure compatibility with Helm v4 ([#&#8203;1038](https://github.com/ansible-collections/kubernetes.core/issues/1038)). - helm\_registry\_auth - Ensure compatibility with Helm v4 ([#&#8203;1038](https://github.com/ansible-collections/kubernetes.core/issues/1038)). - helm\_registry\_auth - add new option plain\_http to allow insecure http connection when running `helm registry login` ([#&#8203;1090](https://github.com/ansible-collections/kubernetes.core/pull/1090)). - helm\_repository - Ensure compatibility with Helm v4 ([#&#8203;1038](https://github.com/ansible-collections/kubernetes.core/issues/1038)). - k8s\_drain - Add support for `check_mode` ([#&#8203;1086](https://github.com/ansible-collections/kubernetes.core/pull/1086)). - k8s\_drain - Convert module warnings into informational displays when users explicitly request the deletion of unmanaged pods, pods with local storage, or those managed by a `DaemonSet` ([#&#8203;1037](https://github.com/ansible-collections/kubernetes.core/issues/1037)). ## Bugfixes - Helm - Allow taking ownership of existing Kubernetes resources on the first installation of a Helm release. Previously, the `take_ownership` parameter was always disabled during the initial install, preventing resource adoption ([#&#8203;1034](https://github.com/ansible-collections/kubernetes.core/pull/1034)). ### [`v6.3.0`](https://github.com/ansible-collections/kubernetes.core/blob/HEAD/CHANGELOG.rst#v630) [Compare Source](https://github.com/ansible-collections/kubernetes.core/compare/6.2.0...6.3.0) \====== ## Release Summary This release includes bugfixes such as implementing idempotency for the `helm_pull` module as well as a security update for selectively redacting sensitive information from kubeconfig. ## Minor Changes - Remove deprecated import from `ansible.module_utils._text` ([#&#8203;1053](https://github.com/ansible-collections/kubernetes.core/pull/1053)). - helm - add `release_values` key to `status` return value that can be accessed using Jinja2 dot notation ([#&#8203;1056](https://github.com/ansible-collections/kubernetes.core/pull/1056)). - helm\_info - add `release_values` key to `status` return value that can be accessed using Jinja2 dot notation ([#&#8203;1056](https://github.com/ansible-collections/kubernetes.core/pull/1056)). ## Deprecated Features - helm - the `status.values` return value has been deprecated and will be removed in a release after 2027-01-08. Use `status.release_values` instead ([#&#8203;1056](https://github.com/ansible-collections/kubernetes.core/pull/1056)). - helm\_info - the `status.values` return value has been deprecated and will be removed in a release after 2027-01-08. Use `status.release_values` instead ([#&#8203;1056](https://github.com/ansible-collections/kubernetes.core/pull/1056)). ## Security Fixes - Selectively redact sensitive info from kubeconfig instead of applying blanket `no_log=True` ([#&#8203;1014](https://github.com/ansible-collections/kubernetes.core/pull/1014)). ## Bugfixes - Add idempotency for `helm_pull` module ([#&#8203;1055](https://github.com/ansible-collections/kubernetes.core/pull/1055)). - Fixed a bug where setting `K8S_AUTH_VERIFY_SSL=true` (or any string value) caused the value to be treated as a separate `kubectl` command argument. ([#&#8203;1049](https://github.com/ansible-collections/kubernetes.core/pull/1049)). - Limit supported versions of Helm to <4.0.0 ([#&#8203;1039](https://github.com/ansible-collections/kubernetes.core/pull/1039)). - Replace passing `warnings` to `exit_json` with `AnsibleModule.warn` in the `k8s_drain`, `k8s_rollback.py` and `k8s_scale.py` modules as it deprecated in `ansible-core>=2.19.0` and will be removed in `ansible-core>=2.23.0` ([#&#8203;1033](https://github.com/ansible-collections/kubernetes.core/pull/1033)). - k8s - Fix return block from the module documentation ([#&#8203;1056](https://github.com/ansible-collections/kubernetes.core/pull/1056)). - meta - Add `k8s_cluster_info`, `k8s_json_patch` and `k8s_rollback` to k8s action group ([#&#8203;992](https://github.com/ansible-collections/kubernetes.core/pull/992)). </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNTMuMSIsInVwZGF0ZWRJblZlciI6IjQzLjI1My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot force-pushed renovate/kubernetes.core-6.x from 35bffcc669 to 525ba732a7 2026-07-08 16:06:46 +00:00 Compare
renovate-bot changed title from Update dependency kubernetes.core to v6.4.0 to Update dependency kubernetes.core to v6.5.0 2026-07-08 16:06:48 +00:00
renovate-bot changed title from Update dependency kubernetes.core to v6.5.0 to chore(deps): update dependency kubernetes.core to v6.5.0 2026-07-17 23:09:47 +00:00
renovate-bot changed title from chore(deps): update dependency kubernetes.core to v6.5.0 to Update dependency kubernetes.core to v6.5.0 2026-07-21 01:07:16 +00:00
renovate-bot changed title from Update dependency kubernetes.core to v6.5.0 to chore(deps): update dependency kubernetes.core to v6.5.0 2026-07-21 02:07:21 +00:00
renovate-bot force-pushed renovate/kubernetes.core-6.x from 525ba732a7 to e856a89450
Some checks failed
ci/crow/pr/dns-test Pipeline failed
ci/crow/pr/tanka-test Pipeline failed
2026-07-22 19:06:23 +00:00
Compare
renovate-bot force-pushed renovate/kubernetes.core-6.x from e856a89450
Some checks failed
ci/crow/pr/dns-test Pipeline failed
ci/crow/pr/tanka-test Pipeline failed
to b146f5f710 2026-09-21 19:12:52 +00:00
Compare
renovate-bot changed title from chore(deps): update dependency kubernetes.core to v6.5.0 to chore(deps): update dependency kubernetes.core to v6.6.0 2026-09-21 19:12:54 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/kubernetes.core-6.x:renovate/kubernetes.core-6.x
git switch renovate/kubernetes.core-6.x

Merge

Merge the changes and update on Forgejo.
git switch main
git merge --no-ff renovate/kubernetes.core-6.x
git switch renovate/kubernetes.core-6.x
git rebase main
git switch main
git merge --ff-only renovate/kubernetes.core-6.x
git switch renovate/kubernetes.core-6.x
git rebase main
git switch main
git merge --no-ff renovate/kubernetes.core-6.x
git switch main
git merge --squash renovate/kubernetes.core-6.x
git switch main
git merge --ff-only renovate/kubernetes.core-6.x
git switch main
git merge renovate/kubernetes.core-6.x
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ops/homelab!18
No description provided.