Update docs to specify workaround for required field: (#11885) (#8332)

[upstream:751f5b65ff52418a88edb748a22a471f429b6d4d] Signed-off-by: Modular Magician <[email protected]>
hashicorp · Oct 2, 2024 · a4ab9c7 · a4ab9c7
1 parent 6072e8e
commit a4ab9c7
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/.changelog/11885.txt b/.changelog/11885.txt
@@ -0,0 +1,3 @@
+```release-note:none
+
+```
diff --git a/website/docs/r/container_cluster.html.markdown b/website/docs/r/container_cluster.html.markdown
@@ -1293,6 +1293,8 @@ Enables monitoring and attestation of the boot integrity of the instance. The at
 * `cpu_manager_policy` - (Optional) The CPU management policy on the node. See
 [K8S CPU Management Policies](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/).
 One of `"none"` or `"static"`. If unset (or set to the empty string `""`), the API will treat the field as if set to "none".
+Prior to the 6.4.0 this field was marked as required. The workaround for the required field 
+is setting the empty string `""`, which will function identically to not setting this field.
 
 * `cpu_cfs_quota` - (Optional) If true, enables CPU CFS quota enforcement for
 containers that specify CPU limits.