OC-ADM-OCP-CERTIFICATES-REGENERATE-TOP-LEVEL(1)

💅 oc adm ocp-certificates regenerate-top-level — regen the top-level certs, bestie

okay so this is a page from the Openshift CLI User Manuals, and it's all about oc adm ocp-certificates regenerate-top-level — the glow-up command for root certificates in an OpenShift cluster. Let's get into it ✨

🦋 SYNOPSIS

oc adm ocp-certificates regenerate-top-level [OPTIONS]

🎀 DESCRIPTION

So basically: this regenerates the root certificates that an OCP v4 cluster provides. Fresh certs, new era, main character energy 👑

Heads up though — this command does not wait for the cluster to acknowledge the changes. Some of these can take a very long time to roll out into a cluster, and there are different operators and operands involved for each one. So like… don't sit there refreshing and panicking, okay? 😭

Experimental: this command is under active development and may change without notice. She's still in her building era, ngl.

---

✨ OPTIONS ✨

• --all=false — select all resources in the namespace of the specified resource types
• -A, --all-namespaces=false — if present, list the requested object(s) across all namespaces. The namespace in the current context gets ignored, even if you specified one with --namespace.
• --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=false — set to true to use server-side dry run
• --field-selector="" — selector (field query) to filter on, supports =, ==, and != (e.g. --field-selector key1=value1,key2=value2). The server only supports a limited number of field queries per type, so don't get too creative 🫶
• -f, --filename=[] — identifying the resource.
• --local=false — if true, annotation will NOT contact api-server but run locally
• -o, --output="" — output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file)
• -R, --recursive=true — process the directory used in -f, --filename recursively. Super useful when you want to manage related manifests organized within the same directory 💖
• -l, --selector="" — selector (label query) to filter on, supports =, ==, and != (e.g. -l key1=value1,key2=value2)
• --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⟩ ]
• --valid-before="" — only regenerate top level certificates valid before this date. Format: 2023-06-05T14:44:06Z

🌸 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 — no cap, that's literally what it does 😬
• --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

ok bestie, here's the moment you've been waiting for — regenerating the signing certificate contained in a particular secret:

# Regenerate the signing certificate contained in a particular secret
oc adm ocp-certificates regenerate-top-level -n openshift-kube-apiserver-operator secret/loadbalancer-serving-signer-key

ate. no crumbs. 🔥

👑 SEE ALSO

• oc-adm-ocp-certificates(1),

💜 HISTORY

June 2016 — Ported from the Kubernetes man-doc generator

---

and that's the whole vibe check 🧚 this was the Openshift CLI User Manuals, June 2016, ported from the Kubernetes man-doc generator — iconic behavior, honestly. bye bestie, go regenerate those certs responsibly 💅✨🍓