Merge pull request #25986 from schollii/master
Clarify binaryData handling by kubectl create and describe
This commit is contained in:
commit
8377d08841
|
|
@ -201,6 +201,9 @@ allow.textmode=true
|
||||||
how.nice.to.look=fairlyNice
|
how.nice.to.look=fairlyNice
|
||||||
```
|
```
|
||||||
|
|
||||||
|
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.
|
||||||
|
If you want to view the `binaryData` keys (and their values) in a ConfigMap, you can run `kubectl get configmap -o jsonpath='{.binaryData}' <name>`.
|
||||||
|
|
||||||
Use the option `--from-env-file` to create a ConfigMap from an env-file, for example:
|
Use the option `--from-env-file` to create a ConfigMap from an env-file, for example:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
|
|
@ -687,4 +690,3 @@ data:
|
||||||
|
|
||||||
* Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/).
|
* Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/).
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue