Merge branch 'main' into node-taint-unique-by-key-and-effect

Author: xinkechen-evernorth

.changelog/2380.txt

@@ -0,0 +1,59 @@
+```release-note:note
+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](https://kubernetes.io/docs/reference/labels-annotations-taints/) since they might be attached to the object by Kubernetes controller and could lead to a perpetual diff.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/). That could lead to a perpetual diff behavior.
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/).
+```
+
+```release-note:bug
+`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](https://kubernetes.io/docs/reference/labels-annotations-taints/).
+```

.changelog/2622.txt

@@ -0,0 +1,3 @@
+```release-note:enhancement
+Add `sub_path_expr` to volume mount options pod spec
+```

.changelog/2699.txt

@@ -0,0 +1,3 @@
+```release-note:bug
+Fixed goroutine-safety in the CRD and metadata cache, resulting in far fewer provider metadata requests.
+```

.changelog/2737.txt

@@ -0,0 +1,3 @@
+```release-note:enhancement
+Add ResourceIdentity support to kubernetes_manifest
+```

.github/workflows/issue-opened.yml

@@ -17,7 +17,7 @@ jobs:
   oncall_review_assigner:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/setup-node@v4
+    - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 #v4.4.0
     - run: npm install @pagerduty/pdjs
     - uses: actions/github-script@e69ef5462fd455e02edcaf4dd7708eda96b9eda0 # v7.0.0
       env:

docs/data-sources/pod.md

@@ -802,6 +802,7 @@ Read-Only:
 - `name` (String)
 - `read_only` (Boolean)
 - `sub_path` (String)
+- `sub_path_expr` (String)
 
 
 
@@ -1321,6 +1322,7 @@ Read-Only:
 - `name` (String)
 - `read_only` (Boolean)
 - `sub_path` (String)
+- `sub_path_expr` (String)
 
 
 

docs/data-sources/pod_v1.md

@@ -802,6 +802,7 @@ Read-Only:
 - `name` (String)
 - `read_only` (Boolean)
 - `sub_path` (String)
+- `sub_path_expr` (String)
 
 
 
@@ -1321,6 +1322,7 @@ Read-Only:
 - `name` (String)
 - `read_only` (Boolean)
 - `sub_path` (String)
+- `sub_path_expr` (String)
 
 
 

docs/resources/cron_job.md

@@ -951,6 +951,7 @@ Optional:
 - `mount_propagation` (String) Mount propagation mode. mount_propagation determines how mounts are propagated from the host to container and the other way around. Valid values are None (default), HostToContainer and Bidirectional.
 - `read_only` (Boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
 - `sub_path` (String) Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+- `sub_path_expr` (String) Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root).
 
 <a id="nestedblock--spec--job_template--spec--template--spec--container--volume_device"></a>
 ### Nested Schema for `spec.job_template.spec.template.spec.container.volume_device`
@@ -1512,6 +1513,7 @@ Optional:
 - `mount_propagation` (String) Mount propagation mode. mount_propagation determines how mounts are propagated from the host to container and the other way around. Valid values are None (default), HostToContainer and Bidirectional.
 - `read_only` (Boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
 - `sub_path` (String) Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+- `sub_path_expr` (String) Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root).
 
 <a id="nestedblock--spec--job_template--spec--template--spec--init_container--volume_device"></a>
 ### Nested Schema for `spec.job_template.spec.template.spec.init_container.volume_device`
@@ -2389,4 +2391,4 @@ resource "kubernetes_cron_job" "demo" {
 
 ```
 $ terraform import kubernetes_cron_job_v1/example default/example
-```
+```

docs/resources/cron_job_v1.md

@@ -946,6 +946,7 @@ Optional:
 - `mount_propagation` (String) Mount propagation mode. mount_propagation determines how mounts are propagated from the host to container and the other way around. Valid values are None (default), HostToContainer and Bidirectional.
 - `read_only` (Boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
 - `sub_path` (String) Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+- `sub_path_expr` (String) Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root).
 
 <a id="nestedblock--spec--job_template--spec--template--spec--container--volume_device"></a>
 ### Nested Schema for `spec.job_template.spec.template.spec.container.volume_device`
@@ -1507,6 +1508,7 @@ Optional:
 - `mount_propagation` (String) Mount propagation mode. mount_propagation determines how mounts are propagated from the host to container and the other way around. Valid values are None (default), HostToContainer and Bidirectional.
 - `read_only` (Boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
 - `sub_path` (String) Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+- `sub_path_expr` (String) Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root).
 
 <a id="nestedblock--spec--job_template--spec--template--spec--init_container--volume_device"></a>
 ### Nested Schema for `spec.job_template.spec.template.spec.init_container.volume_device`

docs/resources/daemon_set_v1.md

@@ -898,6 +898,7 @@ Optional:
 - `mount_propagation` (String) Mount propagation mode. mount_propagation determines how mounts are propagated from the host to container and the other way around. Valid values are None (default), HostToContainer and Bidirectional.
 - `read_only` (Boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
 - `sub_path` (String) Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+- `sub_path_expr` (String) Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root).
 
 <a id="nestedblock--spec--template--spec--container--volume_device"></a>
 ### Nested Schema for `spec.template.spec.container.volume_device`
@@ -1458,6 +1459,7 @@ Optional:
 - `mount_propagation` (String) Mount propagation mode. mount_propagation determines how mounts are propagated from the host to container and the other way around. Valid values are None (default), HostToContainer and Bidirectional.
 - `read_only` (Boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
 - `sub_path` (String) Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+- `sub_path_expr` (String) Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root).
 
 <a id="nestedblock--spec--template--spec--init_container--volume_device"></a>
 ### Nested Schema for `spec.template.spec.init_container.volume_device`