openshift-cli-secrets-unlink man page

openshift cli secrets unlink — Detach secrets from a ServiceAccount

Synopsis

openshift cli secrets unlink [OPTIONS]

Description

Unlink (detach) secrets from a service account

If a secret is no longer valid for a pod, build or image pull, you may unlink it from a service account.

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

 # Unlink a secret currently associated with a service account:
openshift cli secrets unlink serviceaccount-name secret-name another-secret-name ...

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