OC-CONFIG-NEW-KUBELET-BOOTSTRAP-KUBECONFIG(1)
π 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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=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 andnoneis the default, which is lowkey hilarious to me π--profile-output="profile.pprof"β name of the file to write the profile to. it'sprofile.pprofuntil 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
- 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