kubectl create secret docker-registry <NAME>
Create a new secret for use with Docker registries
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 secret to its name |
--docker-email <Email> | Email for Docker registry |
--docker-password <Password> | Password for Docker registry authentication |
--docker-server <Server> | Server location for Docker registry |
--docker-username <Username> | Username for Docker registry authentication |
--from-file <arg> | 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 secret key |
--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 |