OC-CREATE-ROUTE-PASSTHROUGH(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

OC-CREATE-ROUTE-PASSTHROUGH(1) 💅

okay so bestie, this is a page from the Openshift CLI User Manuals — it's oc create route passthrough, and it's literally the glow-up your service deserves. June 2016 energy but the info is timeless, fr fr. ✨

🎀 NAME 🎀

oc create route passthrough — make a route that uses passthrough TLS termination, no cap 💖

🦋 SYNOPSIS 🦋

oc create route passthrough [OPTIONS]

🌸 DESCRIPTION 🌸

Create a route that uses passthrough TLS termination. That's the whole vibe. 🔥

You gotta tell it which service to expose (either just its name, or using the type/name syntax) via the --service flag. Like, it needs to know who the main character is. 👑

✨ 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, iykyk.
  • --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 sending it (window shopping 🛍️). 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 🙈
  • -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 aesthetic 💅
  • --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 the current object will be saved in its annotation. Otherwise the annotation stays unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. future-proofing, iconic.
  • --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). Here's the tea ☕: "true" or "strict" will use a schema to validate the input and fail the request if invalid. It'll 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. choose wisely bestie 😭
  • --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. 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 🚨 (yes, actually insecure, not just a vibe)
  • --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's 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 passthrough route named "my-route" that exposes the frontend service
oc create route passthrough my-route --service=frontend

# Create a passthrough route that exposes the frontend service and specify
# a host name. If the route name is omitted, the service name will be used
oc create route passthrough --service=frontend --hostname=www.example.com

like, look at her go 🫶

🌈 SEE ALSO 🌈

oc-create-route(1),

🧚 HISTORY 🧚

June 2016, Ported from the Kubernetes man-doc generator

and that's the whole page, bestie — love that for us. this little icon was brought to you by Openshift and the Openshift CLI User Manuals, dated June 2016. periodt. 💜🎀

📦 where this page comes from