Merge pull request #32310 from thockin/master
Clarify ConfigMap value type
This commit is contained in:
@@ -42,7 +42,7 @@ that lets you store configuration for other objects to use. Unlike most
|
|||||||
Kubernetes objects that have a `spec`, a ConfigMap has `data` and `binaryData`
|
Kubernetes objects that have a `spec`, a ConfigMap has `data` and `binaryData`
|
||||||
fields. These fields accept key-value pairs as their values. Both the `data`
|
fields. These fields accept key-value pairs as their values. Both the `data`
|
||||||
field and the `binaryData` are optional. The `data` field is designed to
|
field and the `binaryData` are optional. The `data` field is designed to
|
||||||
contain UTF-8 byte sequences while the `binaryData` field is designed to
|
contain UTF-8 strings while the `binaryData` field is designed to
|
||||||
contain binary data as base64-encoded strings.
|
contain binary data as base64-encoded strings.
|
||||||
|
|
||||||
The name of a ConfigMap must be a valid
|
The name of a ConfigMap must be a valid
|
||||||
|
|||||||
Reference in New Issue
Block a user