OC-SERVICEACCOUNTS-NEW-TOKEN(1)

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

πŸ’– OC SERVICEACCOUNTS-NEW-TOKEN β€” like, the manual page πŸ’–

okay so bestie, you're looking at oc serviceaccounts from the OpenShift CLI User Manuals, dated June 2016 β€” yes it's an elder but it still slays ✨

✨ NAME ✨

oc serviceaccounts new-token β€” generate a new token for a service account πŸŽ€

✨ SYNOPSIS ✨

oc serviceaccounts new-token [OPTIONS]

🌸 DESCRIPTION 🌸

Generate a new token for a service account. That's the whole vibe.

So here's the tea: service account API tokens are what service accounts use to authenticate to the API. This command generates a new one, and like… why would you even want that? Three iconic reasons, no cap:

  • to compartmentalize service account actions by executing them with distinct tokens πŸ¦‹
  • to rotate out a pre-existing token on the service account πŸ”„
  • for use by an external client πŸ‘‘

And if you pass a label, it gets applied to any created token, so tokens you made with this command can be identified later. highkey useful iykyk πŸ’…

πŸ’œ OPTIONS πŸ’œ

  • -l, --labels="" β€” labels to set in all resources for this application, given as a comma-delimited list of key-value pairs 🏷️
  • --timeout=0 β€” the maximum time allowed to generate a token ⏳

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

like, these come from the parent command, they're not even ours but we're listing them anyway because periodt πŸ’–

  • --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
  • --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
⚠️ okay warning time: that flag literally makes your HTTPS connections insecure. it's giving "living dangerously" πŸ’€ don't just leave it on for the aesthetic.
  • --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

πŸ¦‹ EXAMPLE πŸ¦‹

watch and learn bestie, two whole examples, we ate:

# Generate a new token for service account 'default'
oc serviceaccounts new-token 'default'

# Generate a new token for service account 'default' and apply
# labels 'foo' and 'bar' to the new token for identification
oc serviceaccounts new-token 'default' --labels foo=foo-value,bar=bar-value

πŸŽ€ SEE ALSO πŸŽ€

🌈 HISTORY 🌈

June 2016, Ported from the Kubernetes man-doc generator β€” vintage, honestly 🫢


and that's the whole page, bestie!! brought to you by Openshift, under Openshift CLI User Manuals, dated June 2016. go forth and generate tokens responsibly πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from