openshift-cli-secrets-new man page

openshift cli secrets new — Create a new secret based on a key file or on files within a directory

Synopsis

openshift cli secrets new [Options]

Description

Create a new secret based on a file or directory

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 create a secret using with all valid keys in that directory.

Options

--confirm=false
Allow unknown secret types.
--no-headers=false
When using the default output, don't print headers.
-o, --output=""
Output format. One of: json|yaml|wide|name|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See golang template [ ⟨http://golang.org/pkg/text/template/#pk…⟩] and jsonpath template [ ⟨http://releases.k8s.io/release-1.3/docs…⟩].
--output-version=""
Output the formatted object with the given group version (for ex: 'extensions/v1beta1').
-q, --quiet=false
Suppress warnings
-a, --show-all=true
When printing, show all resources (false means hide terminated pods.)
--show-labels=false
When printing, show all labels as the last column (default hide labels column)
--sort-by=""
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=""
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/#pk…⟩].
--type=""
The type of secret

Options Inherited from Parent Commands

--api-version=""
DEPRECATED: The API version to use when talking to the server

--as=""
Username to impersonate for the operation.

--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

--config=""
Path to the config file to use for CLI requests.

--context=""
The name of the kubeconfig context to use

--google-json-key=""
The Google Cloud Platform Service Account JSON Key to use for authentication.

--insecure-skip-tls-verify=false
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.

--log-flush-frequency=0
Maximum number of seconds between log flushes

--match-server-version=false
Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request.

--server=""
The address and port of the Kubernetes API server

--token=""
Bearer token for authentication to the API server.

--user=""
The name of the kubeconfig user to use

Example

# Create a new secret named my-secret with a key named ssh-privatekey
openshift cli secrets new my-secret  /.ssh/ssh-privatekey

# Create a new secret named my-secret with keys named ssh-privatekey and ssh-publickey instead of the names of the keys on disk
openshift cli secrets new my-secret ssh-privatekey= /.ssh/id_rsa ssh-publickey= /.ssh/id_rsa.pub

# Create a new secret named my-secret with keys for each file in the folder "bar"
openshift cli secrets new my-secret path/to/bar

# Create a new .dockercfg secret named my-secret
openshift cli secrets new my-secret path/to/.dockercfg

# Create a new .docker/config.json secret named my-secret
openshift cli secrets new my-secret .dockerconfigjson=path/to/.docker/config.json

See Also

openshift-cli-secrets(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

openshift-cli-secrets(1).

Openshift CLI User Manuals Openshift June 2016