OC-CREATE-ROUTE-EDGE(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

🎀 oc create route edge — the manual, but make it make sense 🎀

Okay bestie, so this is oc create route edge, straight out of the Openshift CLI User Manuals (the man-doc generator said hi, we'll get to that at the end 💖). The whole entire vibe of this command? It creates a route that uses edge TLS termination. That's it, that's the main character moment.

✨ SYNOPSIS ✨

oc create route edge [OPTIONS]

🦋 DESCRIPTION 🦋

Create a route that uses edge TLS termination. Periodt.

So like — you gotta tell it which service to expose on the generated route, and you do that with the --service flag. You can pass just the service's name, or you can flex the type/name syntax. Either one slays. 💅

🌸 OPTIONS 🌸

  • --allow-missing-template-keys=true — if true, it just... ignores any errors in templates when a field or map key is missing from the template. No drama, no tears. Only applies to golang and jsonpath output formats, so don't @ it otherwise.
  • --ca-cert="" — path to a CA certificate file. 🎀
  • --cert="" — path to a certificate file.
  • --dry-run="none" — must be "none", "server", or "client". If it's the client strategy, it only prints the object that would be sent, without actually sending it (window shopping, basically 🛍️). If it's the server strategy, it submits a server-side request without persisting the resource.
  • --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.
  • --path="" — path that the router watches to route traffic to the service.
  • --port="" — name of the service port, or the number of the container port that the route will route traffic to.
  • --save-config=false — if true, the configuration of the current object gets saved in its annotation. Otherwise the annotation stays exactly as it is, untouched, unbothered. This flag is lowkey useful when you wanna do kubectl apply on this object in the future. Planning ahead, we love to see it.
  • --service="" — name of the service that the new route is exposing.
  • --show-managed-fields=false — if true, keeps the managedFields when printing objects in JSON or YAML format.
  • --template="" — template string, or path to a template file to use when -o=go-template or -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). Here's the tea ☕:
    • "true" or "strict" uses a schema to validate the input and fails the request if it's invalid. It'll do server-side validation if ServerSideFieldValidation is enabled on the api-server, but falls back to less reliable client-side validation if it's not.
    • "warn" warns about unknown or duplicate fields without blocking the request, if server-side field validation is enabled on the API server — and behaves as "ignore" otherwise.
    • "false" or "ignore" performs no schema validation at all and silently drops any unknown or duplicate fields. 🙈
  • --wildcard-policy="" — sets the WilcardPolicy for the hostname; the default is "None". Valid values are "None" and "Subdomain".

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

  • --as="" — username to impersonate for the operation. 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. Heads up bestie: this will make your HTTPS connections insecure. ⚠️
  • --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 by turning off the feature with 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 the 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" — how long 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 — live in the moment, I guess. ✨
  • -s, --server="" — the address and port of the Kubernetes API server.
  • --tls-server-name="" — server name to use for server certificate validation. If it's not provided, the hostname used to contact the server is used instead.
  • --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 an edge route named "my-route" that exposes the frontend service
oc create route edge my-route --service=frontend

# Create an edge route that exposes the frontend service and specify a path
# If the route name is omitted, the service name will be used
oc create route edge --service=frontend --path /assets

Like, the second one is giving "no name? no problem, the service name is the name now" energy. Iconic. 🌈

💜 SEE ALSO 💜

🍓 HISTORY 🍓

June 2016, ported from the Kubernetes man-doc generator.

aaaand that's the whole page bestie!! 🫶 source/version: Openshift — Openshift CLI User Manuals, dated June 2016 — ok bye, go create some routes, mwah 😭💖

📦 where this page comes from