Skip to content

Conversation

soerenschneider
Copy link
Owner

This PR contains the following updates:

Package Type Update Change
kubernetes (source) required_provider minor 2.37.1 -> 2.38.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

hashicorp/terraform-provider-kubernetes (kubernetes)

v2.38.0

Compare Source

ENHANCEMENTS:

  • Add ResourceIdentity support to kubernetes_manifest [GH-2737]
  • Add sub_path_expr to volume mount options pod spec [GH-2622]
  • Add support for ResourceIdentity to SDKv2 resources [GH-2751]

BUG FIXES:

  • Fixed goroutine-safety in the CRD and metadata cache, resulting in far fewer provider metadata requests. [GH-2699]
  • data_source/kubernetes_pod_v1: fix an issue when the provider cuts out toleration under pod spec(spec.toleration) if it uses a well-known taint. [GH-2380]
  • data_source/kubernetes_pod: fix an issue when the provider cuts out toleration under pod spec(spec.toleration) if it uses a well-known taint. [GH-2380]
  • resource/kubernetes_cron_job: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_cron_job_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_daemon_set_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_daemonset: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_deployment: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_deployment_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_job: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_job_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_replication_controller_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_replication_controller: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_stateful_set: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]
  • resource/kubernetes_stateful_set_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]

NOTES:

  • We have updated the logic of resources that use the Pod specification template, such as kubernetes_deployment_v1, kubernetes_stateful_set_v1, etc, and now the provider will keep all tolerations(spec.toleration) returned by Kubernetes. The same is applicable for the data sources kubernetes_pod_v1 and kubernetes_pod. The behavior of resources kubernetes_pod_v1 and kubernetes_pod remains unchanged, i.e. the provider will keep removing tolerations with well-known taints since they might be attached to the object by Kubernetes controller and could lead to a perpetual diff. [GH-2380]

Configuration

📅 Schedule: 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 is behind base branch, 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 Renovate Bot.

@soerenschneider soerenschneider self-assigned this Jul 22, 2025
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 9 times, most recently from 1953b99 to b5f4f26 Compare July 29, 2025 04:53
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 3 times, most recently from ea92ed8 to 22bb9ce Compare August 6, 2025 08:24
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 3 times, most recently from 2dfd171 to e311b5b Compare August 14, 2025 08:31
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 6 times, most recently from 20ddfda to 3569515 Compare August 22, 2025 08:33
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 2 times, most recently from 2746806 to 6e88931 Compare August 26, 2025 08:32
@soerenschneider soerenschneider changed the title chore(deps): update terraform kubernetes to v2.38.0 Update Terraform kubernetes to v2.38.0 Aug 26, 2025
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch from 6e88931 to 4ee81f0 Compare August 27, 2025 08:27
@soerenschneider soerenschneider changed the title Update Terraform kubernetes to v2.38.0 chore(deps): update terraform kubernetes to v2.38.0 Aug 27, 2025
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 3 times, most recently from 28b817d to a58a49f Compare August 29, 2025 08:28
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 4 times, most recently from 0368652 to 1834c60 Compare September 8, 2025 08:30
@soerenschneider soerenschneider force-pushed the renovate/kubernetes-2.x branch 10 times, most recently from 01e5715 to 8a8e816 Compare September 19, 2025 04:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants