OC-CREATE-USERIDENTITYMAPPING(1)

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

πŸ’– OC CREATE USERIDENTITYMAPPING(1) πŸ’–

okay bestie, so this is from the Openshift CLI User Manuals β€” the June 2016 edition, no cap. it's giving vintage but make it iconic. let's get into it ✨

🌸 NAME 🌸

oc create useridentitymapping β€” manually map an identity to a user, and honestly? sometimes you just gotta do things yourself, yk?

πŸ¦‹ SYNOPSIS πŸ¦‹

oc create useridentitymapping [OPTIONS]

πŸŽ€ DESCRIPTION πŸŽ€

so here's the tea: normally, identities get mapped to users automatically during login. like, the system just handles it for you, slay. but if automatic mapping is turned off (by using the "lookup" mapping method, iykyk), or if you just need to manually establish a mapping between an identity and a user, this command is your new bestie. it creates a user identity mapping object. periodt. πŸ’…

✨ OPTIONS ✨

  • --allow-missing-template-keys=true β€” if true, it just ignores any errors in templates when a field or map key is missing in the template. lowkey forgiving. only applies to golang and jsonpath output formats tho.
  • --dry-run="none" β€” must be "none", "server", or "client". if it's client strategy, it only prints the object that would be sent, without actually sending it (a little preview moment ✨). if it's server strategy, it submits a server-side request without persisting the resource. no strings attached.
  • -o, --output="" β€” output format, bestie. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your vibe.
  • --save-config=false β€” if true, the configuration of the current object gets saved in its annotation. otherwise, the annotation stays unchanged. this flag is useful when you wanna perform kubectl apply on this object in the future. future-proofing, we love to see it πŸ’œ
  • --show-managed-fields=false β€” if true, it keeps the managedFields when printing objects in JSON or YAML format. keep the receipts, basically.
  • --template="" β€” template string or path to template file to use when -o=go-template or -o=go-template-file. the template format is golang templates β€” you can peep the docs at http://golang.org/pkg/text/template/#pkg-overview if you're curious 🧚

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the ones you get from the parent command, like a little inheritance moment πŸ‘‘

  • --as="" β€” username to impersonate for the operation. user could be a regular user or a service account in a namespace. main character energy, but make it someone else.
  • --as-group=[] β€” group to impersonate for the operation. this flag can be repeated to specify multiple groups. collect them all πŸ’…
  • --as-uid="" β€” UID to impersonate for the operation. very specific, very demure.
  • --as-user-extra=[] β€” user extras to impersonate for the operation. this flag can be repeated to specify multiple values for the same key. stacking them up.
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. yes, that's literally the path, no cap.
  • --certificate-authority="" β€” path to a cert file for the certificate authority. trust issues? this is the solution.
  • --client-certificate="" β€” path to a client certificate file for TLS. secure vibes only πŸ”₯
  • --client-key="" β€” path to a client key file for TLS. the key to the kingdom, fr fr.
  • --cluster="" β€” the name of the kubeconfig cluster to use. pick your cluster, bestie.
  • --context="" β€” the name of the kubeconfig context to use. context is everything, literally.
  • --disable-compression=false β€” if true, opt-out of response compression for all requests to the server. sometimes you just want the raw data, yk?
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. ⚠️ this will make your HTTPS connections insecure. proceed with caution, bestie, this is giving risky behavior.
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests. where's your config at?
  • --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. options on options.
  • --match-server-version=false β€” require server version to match client version. gotta match, no mismatches allowed.
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request. stay in your lane (namespace). πŸ’œ
  • --profile="none" β€” name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex). for when you need to profile, bestie.
  • --profile-output="profile.pprof" β€” name of the file to write the profile to. save it for later.
  • --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. patience is a virtue, but zero means forever, apparently.
  • -s, --server="" β€” the address and port of the Kubernetes API server. where's the server at?
  • --tls-server-name="" β€” server name to use for server certificate validation. if it's not provided, the hostname used to contact the server is used. defaults, we love them.
  • --token="" β€” bearer token for authentication to the API server. your ticket in, basically.
  • --user="" β€” the name of the kubeconfig user to use. who are you today?
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code. ⚠️ harsh but fair, honestly.

🌟 EXAMPLE 🌟

# Map the identity "acme_ldap:adamjones" to the user "ajones"
oc create useridentitymapping acme_ldap:adamjones ajones

see? easy. mapping made simple, bestie 🫢

🌸 SEE ALSO 🌸

oc-create(1) β€” go check it out, it's giving related content.

πŸ’« HISTORY πŸ’«

June 2016, Ported from the Kubernetes man-doc generator. a classic, honestly.


and that's the whole thing, bestie! written by the Openshift CLI User Manuals for the Openshift fam, dated June 2016. periodt. πŸ’…βœ¨πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from