chore(deps): update terraform kubernetes to v2.38.0 #134
+25
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/kubernetes-2.x
branch
from
ac9737b to
ebb071c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
=2.24.0->2.38.0Release Notes
hashicorp/terraform-provider-kubernetes (kubernetes)
v2.38.0Compare Source
ENHANCEMENTS:
sub_path_exprto volume mount options pod spec [GH-2622]BUG FIXES:
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:
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 sourceskubernetes_pod_v1andkubernetes_pod. The behavior of resourceskubernetes_pod_v1andkubernetes_podremains 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]v2.37.1Compare Source
BUG FIXES:
GetResourceIdentitySchemasimplementation. [GH-2732]v2.37.0Compare Source
ENHANCEMENTS:
kubernetes_config_map_v1: Add support for ResourceIdentity [GH-2721]v2.36.0Compare Source
ENHANCEMENTS:
resource/kubernetes_secret_v1: Add support for write only attributes fordata_woandbinary_data_wo. [GH-2692]v2.35.1Compare Source
BUG FIXES:
resource/kubernetes_job_v1: revert the changes introduced in v2.34.0, wherettl_seconds_after_finishedwas set to0. [GH-2650]resource/kubernetes_daemon_set_v1: fix issue where fieldsspec.strategy.rolling_update.max_surgeandspec.strategy.rolling_update.max_unavailablewere not being validated correctly. [GH-2653]v2.35.0Compare Source
FEATURES:
resources_kubernetes_daemon_set_v1: Addedmax_surgeargument for torolling_updateblock. [GH-2630]v2.34.0Compare Source
ENHANCEMENTS:
conditionsattribute tokubernetes_nodesdata source, which will provide detailed node health and status information [GH-2612]kubernetes_secret_v1_dataresource to the kubernetes provider. This resource will allow users to manage kubernetes secrets [GH-2604]FEATURES:
kubernetes_certificate_signing_request_v1[GH-2628]kubernetes_token_request_v1[GH-2628]v2.33.0Compare Source
ENHANCEMENTS:
backoff_per_limit_indexandmax_failed_indexesfields instructure_job.go[GH-2421]namespace_selectorfield inPodAffinityTermto enhance pod affinity and anti-affinity rules, allowing selection of namespaces based on label selectors. [GH-2577]kubernetes_manifest- handling "404 Not Found" errors during the deletion of Kubernetes resources, particularly in cases where the resource may have already been deleted by an operator managing the CRD before Terraform attempts to delete it. [GH-2592]schema_container.go: Add VolumeDevices [GH-2573]v2.32.0Compare Source
FEATURES:
kubernetes_server_version[GH-2306]ENHANCEMENTS:
resource/kubernetes_certificate_signing_request_v1: Add argumentspec.expiration_seconds[GH-2559]resource/kubernetes_persistent_volume_v1: supportReadWriteOncePodaccess mode for PVs [GH-2488]v2.31.0Compare Source
ENHANCEMENTS:
v2.30.0Compare Source
BUG FIXES:
data_source/kubernetes_resources: fix an issue where the provider exit with an error when the data sourcekubernetes_resourcesreceives multiple Kubernetes objects containing tuples with different numbers of elements. [GH-2372]kubernetes_manifest: fix issue preventing KUBE_PROXY_URL environment variable from being used in client configuration (#1733) [GH-2485]resource/kubernetes_node_taint: Fix the error check for nonexistant nodes so that terraform does not fail if there is a taint in the state file for a node that has been deleted. [GH-2402]DOCS:
v2.29.0Compare Source
BUG FIXES:
v2.28.1Compare Source
HOTFIX:
manifest_decode(): fix handling of manifests containing null values [GH-2461]v2.28.0Compare Source
ENHANCEMENTS:
NOTE: Using Provider Defined Functions requires Terraform version 1.8.0.
manifest_encode,manifest_decode,manifest_decode_multi[GH-2428]v2.27.0Compare Source
ENHANCEMENTS:
resource/kubernetes_pod_v1: add missingtopology_spread_constraints:node_affinity_policy,node_taints_policy,match_label_keys,min_domains[GH-2429]v2.26.0Compare Source
ENHANCEMENTS:
kubernetes/kubernetes_deployment_v1: Add support forHugePagesinemptyDir.medium[GH-2395]resource/kubernetes_job_v1: add new attributespec.pod_failure_policyto job spec [GH-2394]NOTES:
v2.25.2Compare Source
BUG FIXES:
resource/kubernetes_cron_job_v1: fix an issue when the provider forces a resource recreation after upgrading to2.25.0and2.25.1due to changes in the resource schema. [GH-2387]resource/kubernetes_cron_job: fix an issue when the provider forces a resource recreation after upgrading to2.25.0and2.25.1due to changes in the resource schema. [GH-2387]resource/kubernetes_daemon_set_v1: fix an issue when the provider forces a resource recreation after upgrading to2.25.0and2.25.1due to changes in the resource schema. [GH-2387]resource/kubernetes_daemonset: fix an issue when the provider forces a resource recreation after upgrading to2.25.0and2.25.1due to changes in the resource schema. [GH-2387]resource/kubernetes_stateful_set_v1: fix an issue when the provider forces a resource recreation after upgrading to2.25.0and2.25.1due to changes in the resource schema. [GH-2387]resource/kubernetes_stateful_set: fix an issue when the provider forces a resource recreation after upgrading to2.25.0and2.25.1due to changes in the resource schema. [GH-2387]NOTES:
kubernetes_cron_job_v1andkubernetes_cron_jobgot a new attributespec.job_template.metadata.namespace. It is a stub attribute that does not affect the namespace in which the Pod will be created. The Pod will be created in the same namespace as the main resource. However, modifying this field will force the resource recreation. [GH-2387]kubernetes_stateful_set_v1,kubernetes_stateful_set,kubernetes_daemon_set_v1, andkubernetes_daemonsetgot a new attributespec.template.metadata.namespace. It is a stub attribute that does not affect the namespace in which the Pod will be created. The Pod will be created in the same namespace as the main resource. However, modifying this field will force the resource recreation. [GH-2387]v2.25.1Compare Source
HOTFIX:
kubernetes_manifest: Implement response for GetMetadata protocol function [GH-2384]v2.25.0Compare Source
ENHANCEMENTS:
data_source/kubernetes_persistent_volume_claim_v1: add a new attributespec.volume_mode. [GH-2353]data_source/kubernetes_persistent_volume_claim: add a new attributespec.volume_mode. [GH-2353]kubernetes/schema_stateful_set_spec.go: Addspec.persistentVolumeClaimRetentionPolicyinkubernetes_stateful_set[GH-2333]resource/kubernetes_persistent_volume_claim_v1: add a new attributespec.volume_mode. [GH-2353]resource/kubernetes_persistent_volume_claim: add a new attributespec.volume_mode. [GH-2353]resource/kubernetes_stateful_set_v1: add a new attributespec.volume_claim_template.spec.volume_mode. [GH-2353]resource/kubernetes_stateful_set: add a new attributespec.volume_claim_template.spec.volume_mode. [GH-2353]BUG FIXES:
resource/kubernetes_cron_job_v1: Change the schema to include a namespace injobTemplateresource/kubernetes_stateful_set_v1: Change the schema to include a namespace intemplate[GH-2362]resource/kubernetes_ingress_v1: Fix an issue where the emptytlsattribute in the configuration does not generate the corresponding Ingress object without any TLS configuration. [GH-2344]resource/kubernetes_ingress: Fix an issue where the emptytlsattribute in the configuration does not generate the corresponding Ingress object without any TLS configuration. [GH-2344]NOTES:
ignore_annotationsandignore_labelsprovider settings. In addition to that, a list of ignored labels when they are attached tokubernetes_job(_v1)andkubernetes_cron_job(_v1)resources were extended with labelsbatch.kubernetes.io/controller-uidandbatch.kubernetes.io/job-namesince they aim to replacecontroller-uidandjob-namein the future Kubernetes releases. [GH-2345]A special and warm welcome to the first contribution from our teammate @SarahFrench! 🚀
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.