From f94df3cb36d3afcf51ae9f46e98839af11765788 Mon Sep 17 00:00:00 2001 From: Lee Verberne Date: Wed, 9 Dec 2020 11:34:11 +0100 Subject: [PATCH] Fix formatting error in kubectl debug release note A missing newline after the last list item caused an important note about plugins being hidden to be append to an unrelated note about debugging nodes. --- content/en/blog/_posts/2020-12-08-kubernetes-release-1.20.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/blog/_posts/2020-12-08-kubernetes-release-1.20.md b/content/en/blog/_posts/2020-12-08-kubernetes-release-1.20.md index a5f692e03c..e0fef7ab90 100644 --- a/content/en/blog/_posts/2020-12-08-kubernetes-release-1.20.md +++ b/content/en/blog/_posts/2020-12-08-kubernetes-release-1.20.md @@ -28,6 +28,7 @@ The `kubectl alpha debug` features graduates to beta in 1.20, becoming `kubectl * Troubleshoot workloads that crash on startup by creating a copy of the pod that uses a different container image or command. * Troubleshoot distroless containers by adding a new container with debugging tools, either in a new copy of the pod or using an ephemeral container. (Ephemeral containers are an alpha feature that are not enabled by default.) * Troubleshoot on a node by creating a container running in the host namespaces and with access to the host’s filesystem. + Note that as a new built-in command, `kubectl debug` takes priority over any kubectl plugin named “debug”. You must rename the affected plugin. Invocations using `kubectl alpha debug` are now deprecated and will be removed in a subsequent release. Update your scripts to use `kubectl debug`. For more information about `kubectl debug`, see [Debugging Running Pods](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/).