Kubernetes ConfigMap Operations: Difference between revisions
Jump to navigation
Jump to search
Line 30: | Line 30: | ||
==Use the Content of a File== | ==Use the Content of a File== | ||
The entire content of the file is keyed under the file name | The entire content of the file is keyed by default under the file name. | ||
kubectl create configmap example --from-file=some-config-file.txt | kubectl create configmap example --from-file=some-config-file.txt | ||
Line 45: | Line 45: | ||
shape=circle | shape=circle | ||
</syntaxhighlight> | </syntaxhighlight> | ||
An arbitrary key, different from the file name, can be specified: | |||
kubectl create configmap example --from-file=mykey=some-config-file.txt |
Revision as of 22:15, 22 October 2019
External
Internal
Inspect a ConfigMap
kubectl get cm <name> -o yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: example
...
data:
color: red
shape: square
Create a ConfigMap with CLI
Specify Key/Value Pairs on Command Line
kubectl create configmap example --from-literal=color=red --from-literal=shape=square
Multiple --from-literal=
entries are allowed.
Use the Content of a File
The entire content of the file is keyed by default under the file name.
kubectl create configmap example --from-file=some-config-file.txt
apiVersion: v1
kind: ConfigMap
metadata:
name: example
...
data:
some-config-file.txt: |
color=blue
shape=circle
An arbitrary key, different from the file name, can be specified:
kubectl create configmap example --from-file=mykey=some-config-file.txt