From 26300785f5f6fb12dbf90ae48d70c64e1bda9290 Mon Sep 17 00:00:00 2001 From: Oliver L Schoenborn Date: Wed, 6 Jan 2021 21:33:07 -0500 Subject: [PATCH] Clarify binaryData handling by kubectl create and describe --- .../tasks/configure-pod-container/configure-pod-configmap.md | 2 ++ 1 file changed, 2 insertions(+) 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 2824cce642..1d22c2f3e7 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 @@ -201,6 +201,8 @@ allow.textmode=true how.nice.to.look=fairlyNice ``` +Note that data sources that are not ASCII or UTF-8 will be put in the `binaryData` field of the configmap. Both text and binary data sources can be combined in one configmap, but the `binaryData` field is not displayed (as of kubectl 1.20) by `kubectl describe`. To see the `binaryData` in the configmap, you can use `kubectl get configmap -o json MAP_NAME`. + Use the option `--from-env-file` to create a ConfigMap from an env-file, for example: ```shell