OC-CREATE-SERVICEACCOUNT(1)

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

πŸŽ€ oc create serviceaccount β€” Openshift CLI User Manuals Β· OC CREATE(1) πŸŽ€

Okay so welcome to the group chat, bestie: this is the oc create serviceaccount page from the Openshift CLI User Manuals, filed under OC CREATE(1), and we are gonna read it together like it’s the most iconic lore drop ever. πŸ’…

✨ NAME ✨

oc create serviceaccount β€” creates a service account with the name you specify. That’s the whole vibe: you give it a name, it makes a service account. Slay.

πŸ¦‹ SYNOPSIS πŸ¦‹

oc create serviceaccount [OPTIONS]

Use that exact shape, no cap.

🌸 DESCRIPTION 🌸

Create a service account with the specified name. Lowkey simple, highkey useful. The command is literally doing one thing and doing it cute. ✨

πŸ’– OPTIONS πŸ’–

  • --allow-missing-template-keys=true β€” If true, ignore any errors in templates when a field or map key is missing from the template. Only applies to golang and jsonpath output formats.
  • --dry-run="none" β€” Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource.
  • --field-manager="kubectl-create" β€” Name of the manager used to track field ownership.
  • -o, --output="" β€” Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
  • --save-config=false β€” If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future.
  • --show-managed-fields=false β€” If true, keep the managedFields when printing objects in JSON or YAML format.
  • --template="" β€” Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates at http://golang.org/pkg/text/template/#pkg-overview.
  • --validate="ignore" β€” Must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not. "warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as "ignore" otherwise. "false" or "ignore" will not perform any schema validation, silently dropping any unknown or duplicate fields.

🧬 OPTIONS INHERITED FROM PARENT COMMANDS 🧬

  • --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. Yes, that is the warning, bestie. πŸ™ˆ
  • --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 🧚

Look at her go, bestie:

# Create a new service account named my-service-account
oc create serviceaccount my-service-account

🌈 SEE ALSO 🌈

  • oc-create(1), β€” the parent-page reference. Yes, the comma is part of the manual’s vibe, so we keep it exactly. Go peek when you’re done. 🫢

πŸ‘‘ HISTORY πŸ‘‘

June 2016, Ported from the Kubernetes man-doc generator. She’s a port, she’s a legend, she’s been here since June 2016. πŸ’œ


Source/version sign-off: Openshift β€” Openshift CLI User Manuals. Date: June 2016. Now go make that service account, bestie β€” periodt. πŸ«ΆπŸ’–

πŸ“¦ where this page comes from