kubectl create configmap <NAME>
Create a configmap based on a file, directory, or specified literal value
Arguments
Options
| Name | Description |
|---|
--allow-missing-template-keys | If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats |
--dry-run <Strategy> | Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource |
-o, --output <Output Format> | Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-file |
--template <arg> | Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview] |
--append-hash | Append a hash of the configmap to its name |
--from-env-file <arg> | Specify the path to a file to read lines of key=val pairs to create a configmap (i.e. a Docker .env file) |
--from-file <arg> | Key file can be specified using its file path, in which case file basename will be used as configmap key, or optionally with a key and file path, in which case the given key will be used. Specifying a directory will iterate each named file in the directory whose basename is a valid configmap key |
--from-literal <key=value> | Specify a key and literal value to insert in configmap (i.e. mykey=somevalue) |
--save-config | If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future |
--validate | If true, use a schema to validate the input before sending it |