Skip to content

Commit c398ae4

Browse files
scholliiTim Bannister
andauthored
Update content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Co-authored-by: Tim Bannister <[email protected]>
1 parent 2630078 commit c398ae4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,8 @@ allow.textmode=true
201201
how.nice.to.look=fairlyNice
202202
```
203203

204-
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`.
204+
When `kubectl` creates a ConfigMap from inputs that are not ASCII or UTF-8, the tool puts these into the `binaryData` field of the ConfigMap, and not in `data`. Both text and binary data sources can be combined in one ConfigMap.
205+
If you want to view the `binaryData` keys (and their values) in a ConfigMap, you can run `kubectl get configmap -o jsonpath='{.binaryData}' <name>`.
205206

206207
Use the option `--from-env-file` to create a ConfigMap from an env-file, for example:
207208

@@ -689,4 +690,3 @@ data:
689690

690691
* Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/).
691692

692-

0 commit comments

Comments
 (0)