openshift-cli-secrets-link man page

openshift cli secrets link — Link secrets to a ServiceAccount

Synopsis

openshift cli secrets link [Options]

Description

Link secrets to a service account

Linking a secret enables a service account to automatically use that secret for some forms of authentication.

Options

--for=[mount]

type of secret to link: mount or pull

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

--azure-container-registry-config=""

Path to the file container Azure container registry configuration information.

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

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

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

  # Add an image pull secret to a service account to automatically use it for pulling pod images:
  openshift cli secrets link serviceaccount-name pull-secret --for=pull
  
  # Add an image pull secret to a service account to automatically use it for both pulling and pushing build images:
  openshift cli secrets link builder builder-image-secret --for=pull,mount
  
  # If the cluster's serviceAccountConfig is operating with limitSecretReferences: True, secrets must be added to the pod's service account whitelist in order to be available to the pod:
  openshift cli secrets link pod-sa pod-secret

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