KUBERNETES(1)(kubernetes)

πŸ“¦ version 1.35.8, in fedora 43, fedora 44

✨ KUBERNETES(1)(kubernetes) ✨

okay bestie, pull up a chair πŸ’– this is a page from the kubernetes manual, section 1 (that's the "user commands" section, iykyk), and it's genuinely so useful. let's get into it 🫢


🌸 NAME 🌸

kubectl alpha kuberc view β€” Display the current kuberc configuration

like, literally just show you your kuberc config. that's the whole vibe πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

kubectl alpha kuberc view [OPTIONS]

no positional args, no drama, just options. periodt.


πŸ¦‹ DESCRIPTION πŸ¦‹

Display the contents of the kuberc file in the specified output format.

that's it. that's the plot. you point it at a kuberc file (or it finds the default one for you) and it prints what's inside in whatever format you asked for ✨


πŸ’– OPTIONS πŸ’–

  • --allow-missing-template-keys=true β€” If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
  • --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.
  • -o, --output="yaml" β€” Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
  • --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 [http://golang.org/pkg/text/template/#pkg-overview].

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the ones you didn't ask for but got anyway, because your parent commands love you and also love sharing ✨

  • --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="/home/username/.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
🚨 bestie. read that one again. "insecure" is not a vibe, it is a warning. do not be doing this casually, fr fr.
  • --kubeconfig="" β€” Path to the kubeconfig file to use for CLI requests.
  • --match-server-version=false β€” Require server version to match client version
  • -n, --namespace="" β€” If present, the namespace scope for this CLI request
  • --password="" β€” Password for basic authentication to the API server
  • --profile="none" β€” Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace)
  • --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
  • --username="" β€” Username for basic authentication to the API server
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version
  • --warnings-as-errors=false β€” Treat warnings received from the server as errors and exit with a non-zero exit code

πŸ’… EXAMPLE πŸ’…

the receipts, as requested πŸ‘‘

# View kuberc configuration in YAML format (default)
kubectl alpha kuberc view

# View kuberc configuration in JSON format
kubectl alpha kuberc view --output json

# View a specific kuberc file
kubectl alpha kuberc view --kuberc /path/to/kuberc

see how the default is YAML? iconic. no extra flags needed, she just works 🧚


πŸ”₯ SEE ALSO πŸ”₯

that's the whole family tree, go read that one too if you're nosy (respectfully) πŸ’œ


πŸ‘‘ HISTORY πŸ‘‘

January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!

ngl the "hopefully they have been automatically generated since" line is sending me 😭 the original author was out here manifesting automation in 2015 and honestly? valid.


and that's the whole page, bestie!! this came out of the Manuals / User corner of the docs β€” specifically the KUBERNETES(1)(kubernetes) page, dated Jan 2015 🌸 go forth and view your kuberc, you absolute main character πŸ¦‹βœ¨πŸ’–

πŸ“¦ where this page comes from