OC-SECRETS-UNLINK(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

okay so this is the manual page for oc secrets unlink, from the OpenShift CLI User Manuals fam β€” filed under OC SECRETS(1), dated June 2016. yes i know, ancient. it still serves πŸ’…


πŸŽ€ NAME πŸŽ€

oc secrets unlink β€” the one where you detach secrets from a service account. that's the whole vibe. unlinking. letting go. main character breakup energy πŸ¦‹


✨ SYNOPSIS ✨

oc secrets unlink [OPTIONS]

πŸ’– DESCRIPTION πŸ’–

so like β€” you unlink (aka detach, aka "we're not together anymore") secrets from a service account. that's it. that's the function 🫢

and if a secret is no longer valid for a pod, build or image pull? you may unlink it from a service account. simple as. no cap 🧚


🌸 OPTIONS 🌸

  • --allow-missing-template-keys=true β€” if true, it'll ignore any errors in templates when a field or map key is missing in the template. important caveat bestie: this only applies to golang and jsonpath output formats. only those. not the others πŸ™ˆ
  • -o, --output="" β€” the output format, pick one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). that's the list, i don't make the rules ✨
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format πŸ’…
  • --template="" β€” a template string, or path to a 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] β€” literally linked for u πŸŽ€

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these come from the parent commands, they're the inherited genes of this command fr fr 🧬

  • --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.
  • --as-user-extra=[] β€” user extras to impersonate for the operation, this flag can be repeated to specify multiple values for the same key.
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. yes that's the actual default path, don't ask 😭
  • --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 ⚠️ like, actually. don't be casual with this one.
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests.
  • --kuberc="" β€” path to the kuberc file to use for preferences. this can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off.
  • --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. stern queen behavior πŸ’€

πŸ”₯ EXAMPLE πŸ”₯

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

look at that. one service account, then as many secret names as you want. go off πŸ‘‘


πŸ¦‹ SEE ALSO πŸ¦‹


⭐ HISTORY ⭐

June 2016 β€” ported from the Kubernetes man-doc generator. ancient lore 🏺


and that's the whole page bestie πŸ’œ sign-off time: this was brought to you by Openshift, from the Openshift CLI User Manuals, dated June 2016. slay, hydrate, and read ur man pages πŸ“βœ¨

πŸ“¦ where this page comes from