OC-CONFIG-NEW-KUBELET-BOOTSTRAP-KUBECONFIG(1)

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

πŸ’… OC-CONFIG-NEW-KUBELET-BOOTSTRAP-KUBECONFIG(1) β€” the glow-up guide ✨

okay so bestie, welcome to OC CONFIG(1), the OpenShift CLI User Manuals situation β€” June 2016 coded but the knowledge is timeless, fr fr. This one's all about one very specific lil subcommand and honestly? She's iconic for it. πŸŽ€


✨ NAME ✨

oc config new-kubelet-bootstrap-kubeconfig β€” literally generates a brand new kubelet /etc/kubernetes/kubeconfig, makes the server trust it, and then shows it off to you. Three-step slay. πŸ’…


🌸 SYNOPSIS 🌸

oc config new-kubelet-bootstrap-kubeconfig [OPTIONS]

that's it. that's the whole vibe. no positional args, just you and your [OPTIONS] besties. πŸ¦‹


πŸ’– DESCRIPTION πŸ’–

so what does she actually do? Generate, make the server trust, and display a new kubelet /etc/kubernetes/kubeconfig. Like, in that exact order. She generates it, she gets the server to trust it (obsessed with the trust-building arc 😭), and then she displays it for you. main character energy from start to finish, no cap. πŸ‘‘


🫢 OPTIONS INHERITED FROM PARENT COMMANDS 🫢

these are all the flags she got from the parent command β€” she didn't invent them, she inherited them, and honestly that's valid. every single one, coming right up, no skipping: ⭐

  • --as="" β€” username to impersonate for the operation. could be a regular user, could be a service account in a namespace. either way, you're someone else now πŸ’€
  • --as-group=[] β€” group to impersonate for the operation. this flag can be repeated to specify multiple groups. spamming allowed, encouraged even πŸŽ€
  • --as-uid="" β€” UID to impersonate for the operation. yes, the UID specifically. very specific of her.
  • --as-user-extra=[] β€” user extras to impersonate for the operation. this flag can be repeated to specify multiple values for the same key. so like, multiple extras, same key. iykyk ✨
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. yes, that's the literal default path, no i'm not joking πŸ™ˆ
  • --certificate-authority="" β€” path to a cert file for the certificate authority. trust issues, but make it TLS. πŸ”₯
  • --client-certificate="" β€” path to a client certificate file for TLS. one half of the iconic duo πŸ’œ
  • --client-key="" β€” path to a client key file for TLS. the other half. keep them together or it's giving chaos.
  • --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. uncompressed and unbothered.
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. and this will make your HTTPS connections insecure. like, actually insecure, not cute-insecure. ⚠️ treat her with respect.
  • --kubeconfig="" β€” use a particular kubeconfig file. your particular one. special treatment. πŸ’–
  • --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. two whole ways to turn it off, generous queen πŸŽ€
  • --match-server-version=false β€” require server version to match client version. if you're into that kind of strictness, slay.
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request. short flag, big impact. πŸ’…
  • --profile="none" β€” name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex). so many options and none is the default, which is lowkey hilarious to me 😭
  • --profile-output="profile.pprof" β€” name of the file to write the profile to. it's profile.pprof until you say otherwise. ⭐
  • --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. zero = no patience limits = she's patient actually 🧚
  • -s, --server="" β€” the address and port of the Kubernetes API server. where we're headed πŸ—ΊοΈ
  • --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. she'll figure it out herself, don't worry.
  • --token="" β€” bearer token for authentication to the API server. your lil backstage pass πŸ”‘
  • --user="" β€” the name of the kubeconfig user to use. pick your user, be someone. πŸ‘‘
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code. turning the volume UP on warnings, dramatic but fair πŸ’€

πŸ”₯ EXAMPLE πŸ”₯

here's the moment you've been waiting for, the actual demo bestie:

# Generate a new kubelet bootstrap kubeconfig
oc config new-kubelet-bootstrap-kubeconfig

that's literally the whole thing. one line. she ate and left no crumbs. ✨


🌈 SEE ALSO 🌈

go read the parent page too, family reunion vibes 🫢


πŸŽ€ HISTORY πŸŽ€

June 2016, Ported from the Kubernetes man-doc generator. a vintage moment, truly. πŸ¦‹


okay that's the whole page!! πŸ’– this came to you from Openshift and the Openshift CLI User Manuals (same name, both sides, iconic symmetry), version-date June 2016, manual OC CONFIG(1). drink some water, go make that bootstrap kubeconfig, and stan responsibly. mwah πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from