From 2e73eb307bec4f405aa14183fb91e07c0ef68af9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Arda=20G=C3=BC=C3=A7l=C3=BC?= Date: Thu, 11 Jul 2024 16:50:12 +0300 Subject: [PATCH] Update content/en/blog/_posts/2024-06-21-custom-profiling-kubectl-debug.md Co-authored-by: Maciej Szulik --- .../en/blog/_posts/2024-06-21-custom-profiling-kubectl-debug.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2024-06-21-custom-profiling-kubectl-debug.md b/content/en/blog/_posts/2024-06-21-custom-profiling-kubectl-debug.md index 425ef21ab5..84536e8f83 100644 --- a/content/en/blog/_posts/2024-06-21-custom-profiling-kubectl-debug.md +++ b/content/en/blog/_posts/2024-06-21-custom-profiling-kubectl-debug.md @@ -40,7 +40,7 @@ for advanced troubleshooting?. There is no mechanism to achieve this. ## Custom Profiling -Custom profiling is a new flag, namely `custom`, introduced in kubectl debug to provide extensibility. It expects partial `Container` spec in either YAML or JSON format. +Custom profiling is a new functionality available under `--custom` flag, introduced in kubectl debug to provide extensibility. It expects partial `Container` spec in either YAML or JSON format. In order to debug the example-container above by creating an ephemeral container, we simply have to define this YAML: ```yaml