99 lines
6.0 KiB
Markdown
99 lines
6.0 KiB
Markdown
---
|
|
---
|
|
|
|
## kubectl create configmap
|
|
|
|
Create a configmap from a local file, directory or literal value
|
|
|
|
### Synopsis
|
|
|
|
|
|
|
|
Create a configmap based on a file, directory, or specified literal value.
|
|
|
|
A single configmap may package one or more key/value pairs.
|
|
|
|
When creating a configmap based on a file, the key will default to the basename of the file, and the value will
|
|
default to the file content. If the basename is an invalid key, you may specify an alternate key.
|
|
|
|
When creating a configmap based on a directory, each file whose basename is a valid key in the directory will be
|
|
packaged into the configmap. Any directory entries except regular files are ignored (e.g. subdirectories,
|
|
symlinks, devices, pipes, etc).
|
|
|
|
|
|
```
|
|
kubectl create configmap NAME [--from-file=[key=]source] [--from-literal=key1=value1] [--dry-run]
|
|
```
|
|
|
|
### Examples
|
|
|
|
```
|
|
|
|
# Create a new configmap named my-config with keys for each file in folder bar
|
|
kubectl create configmap my-config --from-file=path/to/bar
|
|
|
|
# Create a new configmap named my-config with specified keys instead of names on disk
|
|
kubectl create configmap my-config --from-file=key1=/path/to/bar/file1.txt --from-file=key2=/path/to/bar/file2.txt
|
|
|
|
# Create a new configmap named my-config with key1=config1 and key2=config2
|
|
kubectl create configmap my-config --from-literal=key1=config1 --from-literal=key2=config2
|
|
```
|
|
|
|
### Options
|
|
|
|
```
|
|
--dry-run If true, only print the object that would be sent, without sending it.
|
|
--from-file value Key files can be specified using their file path, in which case a default name will be given to them, or optionally with a name and file path, in which case the given name will be used. Specifying a directory will iterate each named file in the directory that is a valid configmap key. (default [])
|
|
--from-literal value Specify a key and literal value to insert in configmap (i.e. mykey=somevalue) (default [])
|
|
--generator string The name of the API generator to use. (default "configmap/v1")
|
|
--no-headers When using the default or custom-column output format, don't print headers.
|
|
-o, --output string Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [http://kubernetes.io/docs/user-guide/kubectl-overview/#custom-columns], golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [http://kubernetes.io/docs/user-guide/jsonpath].
|
|
--output-version string Output the formatted object with the given group version (for ex: 'extensions/v1beta1').
|
|
--save-config If true, the configuration of current object will be saved in its annotation. This is useful when you want to perform kubectl apply on this object in the future.
|
|
--schema-cache-dir string If non-empty, load/store cached API schemas in this directory, default is '$HOME/.kube/schema' (default "~/.kube/schema")
|
|
-a, --show-all When printing, show all resources (default hide terminated pods.)
|
|
--show-labels When printing, show all labels as the last column (default hide labels column)
|
|
--sort-by string If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string.
|
|
--template string 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].
|
|
--validate If true, use a schema to validate the input before sending it (default true)
|
|
```
|
|
|
|
### Options inherited from parent commands
|
|
|
|
```
|
|
--alsologtostderr value log to standard error as well as files
|
|
--as string Username to impersonate for the operation
|
|
--certificate-authority string Path to a cert. file for the certificate authority
|
|
--client-certificate string Path to a client certificate file for TLS
|
|
--client-key string Path to a client key file for TLS
|
|
--cluster string The name of the kubeconfig cluster to use
|
|
--context string The name of the kubeconfig context to use
|
|
--insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
|
|
--kubeconfig string Path to the kubeconfig file to use for CLI requests.
|
|
--log-backtrace-at value when logging hits line file:N, emit a stack trace (default :0)
|
|
--log-dir value If non-empty, write log files in this directory
|
|
--logtostderr value log to standard error instead of files
|
|
--match-server-version Require server version to match client version
|
|
-n, --namespace string If present, the namespace scope for this CLI request
|
|
--password string Password for basic authentication to the API server
|
|
-s, --server string The address and port of the Kubernetes API server
|
|
--stderrthreshold value logs at or above this threshold go to stderr (default 2)
|
|
--token string Bearer token for authentication to the API server
|
|
--user string The name of the kubeconfig user to use
|
|
--username string Username for basic authentication to the API server
|
|
-v, --v value log level for V logs
|
|
--vmodule value comma-separated list of pattern=N settings for file-filtered logging
|
|
```
|
|
|
|
|
|
|
|
###### Auto generated by spf13/cobra on 2-Sep-2016
|
|
|
|
|
|
|
|
|
|
|
|
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
|
[]()
|
|
<!-- END MUNGE: GENERATED_ANALYTICS -->
|