Upgrade guide: Stop deleting failed GKE clusters, taint instead (#8986)…

… (#6302) Signed-off-by: Modular Magician <[email protected]>
hashicorp · Sep 18, 2023 · a65af2f · a65af2f
1 parent 5c58da1
commit a65af2f
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 1 deletion.
diff --git a/.changelog/8986.txt b/.changelog/8986.txt
@@ -0,0 +1,2 @@
+```release-note:none
+```
diff --git a/website/docs/guides/version_5_upgrade.html.markdown b/website/docs/guides/version_5_upgrade.html.markdown
@@ -279,6 +279,15 @@ This unsupported field was introduced incorrectly. It is now removed.
 
 ## Resource: `google_container_cluster`
 
+### Clusters created in error states are now tainted rather than deleted
+
+GKE clusters that are created but do not become healthy will now be recorded in
+state and marked as tainted for cleanup on next apply rather than immediately
+deleted.
+
+This behavior was changed to allow users to collect internal logs from the
+cluster and/or manually resolve the issues and untaint their failed clusters.
+
 ### `enable_binary_authorization` is now removed
 
 `enable_binary_authorization` has been removed in favor of `binary_authorization.enabled`.
@@ -515,4 +524,4 @@ resource "google_secret_manager_secret" "my-secret" {
 
 ### `google_identity_platform_project_default_config` has been removed from the provider
 
-Use the `google_identity_platform_config` resource instead. It contains a more comprehensive list of fields, and was created before `google_identity_platform_project_default_config` was added.
+Use the `google_identity_platform_config` resource instead. It contains a more comprehensive list of fields, and was created before `google_identity_platform_project_default_config` was added.