OC-SECRETS-UNLINK(1)
π OC SECRETS(1) β oc secrets unlink, bestie edition β¨
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 togolangandjsonpathoutput 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 themanagedFieldswhen 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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=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
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms