From 00984b38b76a3e241f9a95f720b789e1ab9c618e Mon Sep 17 00:00:00 2001 From: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com> Date: Thu, 21 Jul 2022 07:49:41 +0100 Subject: [PATCH] Update content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md Co-authored-by: Tim Bannister --- .../tasks/configure-pod-container/configure-pod-configmap.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md b/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md index c13fc2ce6a..668db33f09 100644 --- a/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md +++ b/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md @@ -684,7 +684,8 @@ If the ConfigMap exists, but the referenced key is non-existent the path will be #### Optional ConfigMap in environment variables There might be situations where environment variables are not always required. -These environment variables can be marked as optional in a pod like so: +You can mark an environment variables for a container as optional, +like this: ```yaml apiVersion: v1