OC-CREATE-ROUTE-REENCRYPT(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

🦋 OC CREATE ROUTE(1) 🦋

okay bestie, so this is oc create route reencrypt from the Openshift CLI User Manuals — yes, the whole manual is literally called Openshift CLI User Manuals, iconic naming, no notes. dated June 2016, still serving looks. let's get into it 💅

✨ NAME ✨

oc create route reencrypt — literally just creates a route that uses reencrypt TLS termination. that's the whole vibe. 🎀

✨ SYNOPSIS ✨

oc create route reencrypt [OPTIONS]

🌸 DESCRIPTION 🌸

Create a route that uses reencrypt TLS termination. simple as that, queen. 👑

You tell it which service the generated route should expose using the --service flag — you can pass just the service name, or use the type/name syntax if you're feeling fancy. 🫶

You may also specify a destination CA certificate with the --dest-ca-cert flag. and here's the tea: if you omit --dest-ca-cert, the route will use the service CA, which means the service must use a serving certificate from the serving cert signer. that's a real requirement, not a suggestion, ngl. 😭

💖 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. (so it's a template-only little guy, don't @ me) ✨
  • --ca-cert="" — path to a CA certificate file.
  • --cert="" — path to a certificate file.
  • --dest-ca-cert="" — path to a CA certificate file, used for securing the connection from the router to the destination. defaults to the Service CA. 🔥
  • --dry-run="none" — must be "none", "server", or "client". if client strategy, only print the object that would be sent, without sending it. if server strategy, submit server-side request without persisting the resource. (like a dress rehearsal, but for your route 🎀)
  • --hostname="" — set a hostname for the new route
  • --insecure-policy="" — set an insecure policy for the new route
  • --key="" — path to a key file.
  • -o, --output="" — output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your fighter 💅
  • --path="" — path that the router watches to route traffic to the service.
  • --port="" — name of the service port or number of the container port the route will route traffic to
  • --save-config=false — if true, the configuration of current object will be saved in its annotation. otherwise, the annotation will be unchanged. this flag is useful when you want to perform kubectl apply on this object in the future. (future-you says thank you 🫶)
  • --service="" — name of the service that the new route is exposing
  • --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].
  • --validate="ignore" — must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate the input and fail the request if invalid — it will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not. "warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as "ignore" otherwise. "false" or "ignore" will not perform any schema validation, silently dropping any unknown or duplicate fields. ⭐
  • --wildcard-policy="" — sets the WilcardPolicy for the hostname, the default is "None". valid values are "None" and "Subdomain". (yes, WilcardPolicy with one D — that's how it's spelled here, do not come for me 🙈)

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these are the family heirlooms, bestie — inherited, not invented. every single one carries over:

  • --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. (/homeless-shelter is genuinely the path, I'm not being dramatic 😭)
  • --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 — like, actually insecure, be so serious before you flip this one 🔥💀
  • --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 🌈

# Create a route named "my-route" that exposes the frontend service
oc create route reencrypt my-route --service=frontend --dest-ca-cert cert.cert

# Create a reencrypt route that exposes the frontend service, letting the
# route name default to the service name and the destination CA certificate
# default to the service CA
oc create route reencrypt --service=frontend

ate. both examples. copy-paste ready, bestie 🫶

🎀 SEE ALSO 🎀

(that trailing comma is in the original, so it stays. we respect the source ✨)

👑 HISTORY 👑

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

and that's the page, bestie 💜 — brought to you by Openshift, from the Openshift CLI User Manuals, dated June 2016, filed under OC CREATE ROUTE(1). go forth and reencrypt, you absolute icon 🌸💅

📦 where this page comes from