table of contents
OC CREATE SECRET(1) | June 2016 | OC CREATE SECRET(1) |
NAME¶
oc create secret docker-registry - Create a secret for use with a Docker registry
SYNOPSIS¶
oc create secret docker-registry [OPTIONS]
DESCRIPTION¶
Create a new secret for use with Docker registries.
Dockercfg secrets are used to authenticate against Docker registries.
When using the Docker command line to push images, you can authenticate to a given registry by running:
'$ docker login DOCKER_REGISTRY_SERVER --username=DOCKER_USER --password=DOCKER_PASSWORD --email=DOCKER_EMAIL'.
That produces a /.dockercfg file that is used by subsequent 'docker push' and 'docker pull' commands to authenticate to the registry. The email address is optional.
When creating applications, you may have a Docker registry that requires authentication. In order for the
nodes to pull images on your behalf, they must have the credentials. You can provide this information
by creating a dockercfg secret and attaching it to your service account.
OPTIONS¶
--allow-missing-template-keys=true
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.
--append-hash=false
Append a hash of the secret to its name.
--docker-email=""
Email for Docker registry
--docker-password=""
Password for Docker registry authentication
--docker-server="
⟨https://index.docker.io/v1/"⟩
Server location for Docker registry
--docker-username=""
Username for Docker registry authentication
--dry-run="none"
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.
--field-manager="kubectl-create"
Name of the manager used to track field ownership.
--from-file=[]
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.
-o, --output=""
Output format. One of: (json, yaml, name, go-template, go-template-file,
template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
--save-config=false
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.
--show-managed-fields=false
If true, keep the managedFields when printing objects in JSON or YAML
format.
--template=""
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="ignore"
Must be one of: strict (or true), warn, ignore (or false).
"true" or "strict" will use a schema to validate the
input and fail the request if invalid. It will perform server side
validation if ServerSideFieldValidation is enabled on the api-server, but
will fall back to less reliable client-side validation if not.
"warn" will warn about unknown or duplicate fields without blocking
the request if server-side field validation is enabled on the API server,
and behave as "ignore" otherwise.
"false" or "ignore" will not perform any schema
validation, silently dropping any unknown or duplicate fields.
OPTIONS INHERITED FROM PARENT COMMANDS¶
--as=""
Username to impersonate for the operation. User could be a regular user or a
service account in a namespace.
--as-group=[]
Group to impersonate for the operation, this flag can be repeated to specify
multiple groups.
--as-uid=""
UID to impersonate for the operation.
--cache-dir="/home/abuild/.kube/cache"
Default cache directory
--certificate-authority=""
Path to a cert file for the certificate authority
--client-certificate=""
Path to a client certificate file for TLS
--client-key=""
Path to a client key file for TLS
--cluster=""
The name of the kubeconfig cluster to use
--context=""
The name of the kubeconfig context to use
--disable-compression=false
If true, opt-out of response compression for all requests to the server
--insecure-skip-tls-verify=false
If true, the server's certificate will not be checked for validity. This will
make your HTTPS connections insecure
--kubeconfig=""
Path to the kubeconfig file to use for CLI requests.
--match-server-version=false
Require server version to match client version
-n, --namespace=""
If present, the namespace scope for this CLI request
--profile="none"
Name of profile to capture. One of
(none|cpu|heap|goroutine|threadcreate|block|mutex)
--profile-output="profile.pprof"
Name of the file to write the profile to
--request-timeout="0"
The length of time to wait before giving up on a single server request.
Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h).
A value of zero means don't timeout requests.
-s, --server=""
The address and port of the Kubernetes API server
--tls-server-name=""
Server name to use for server certificate validation. If it is not provided,
the hostname used to contact the server is used
--token=""
Bearer token for authentication to the API server
--user=""
The name of the kubeconfig user to use
--warnings-as-errors=false
Treat warnings received from the server as errors and exit with a non-zero
exit code
EXAMPLE¶
# If you do not already have a .dockercfg file, create a dockercfg secret directly
oc create secret docker-registry my-secret --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL
# Create a new secret named my-secret from /.docker/config.json
oc create secret docker-registry my-secret --from-file=.dockerconfigjson=path/to/.docker/config.json
SEE ALSO¶
HISTORY¶
June 2016, Ported from the Kubernetes man-doc generator
Openshift CLI User Manuals | Openshift |