Kubernetes ConfigMap Manifest: Difference between revisions
Jump to navigation
Jump to search
Line 33: | Line 33: | ||
=Elements= | =Elements= | ||
==<tt>data</tt>== | ==<tt>data</tt>== | ||
Data contains the configuration data. Each key must consist of alphanumeric characters, '-', '_' or '.'. Values with non-UTF-8 byte sequences must use the <code>[[#binaryData|binaryData]]</code> field. The keys stored in <code>[[#data|data]]</code> must not overlap with the keys in the <code>[[#binaryData|binaryData]]</code> field, this is enforced during validation process. | |||
==<tt>binaryData</tt>== | |||
==<tt>immutable</tt>== |
Revision as of 17:50, 2 March 2022
External
Internal
Example
apiVersion: v1 kind: ConfigMap metadata: name: blue labels: color: blue annotations: ... data: # property-like keys; each key maps to a simple value quantity: "3" file_name: "somefile.properties" # file-like keys game.properties: | shape=square strength=5 somefile.properties: | color.good=purple color.bad=yellow allow.textmode=true binaryData: immutable: true|false
Elements
data
Data contains the configuration data. Each key must consist of alphanumeric characters, '-', '_' or '.'. Values with non-UTF-8 byte sequences must use the binaryData
field. The keys stored in data
must not overlap with the keys in the binaryData
field, this is enforced during validation process.