OC-CREATE-INGRESS(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

🌈 OC-CREATE-INGRESS(1) — oc create ingress, bestie 🌈

okay so welcome to the oc create ingress page from the OpenShift CLI User Manuals, manual name OC-CREATE-INGRESS(1). It’s giving “make an ingress with the specified name,” and honestly? slay. 💅

✨ NAME ✨

oc create ingress — create an ingress with the specified name. periodt. 👑

🦋 SYNOPSIS 🦋

oc create ingress [OPTIONS]

🌸 DESCRIPTION 🌸

Create an ingress with the specified name. that’s the whole vibe. no cap, it’s a little command with a lot of main-character energy. ✨

💅 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. 🫶
  • --annotation=[] — annotation to insert in the ingress object, in the format annotation=value. 🎀
  • --class="" — Ingress Class to be used. 👑
  • --default-backend="" — default service for backend, in format of svcname:port. 🌟
  • --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. 💀
  • --field-manager="kubectl-create" — name of the manager used to track field ownership. 🧚
  • -o, --output="" — output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). 🌈
  • --rule=[] — rule in format host/path=service:port[,tls=secretname]. Paths containing the leading character '*' are considered pathType=Prefix. tls argument is optional. 🔥
  • --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. 🍓
  • --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. 😭
🫶 real talk: --rule paths with the leading * are considered pathType=Prefix, and the tls argument is optional. iykyk.

🧬 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. 💀
  • --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 🌟

bestie, these are the exact examples. copy-paste responsibly. 💖

# Create a single ingress called 'simple' that directs requests to foo.com/bar to svc
# svc1:8080 with a TLS secret "my-cert"
oc create ingress simple --rule="foo.com/bar=svc1:8080,tls=my-cert"

# Create a catch all ingress of "/path" pointing to service svc:port and Ingress Class as "otheringress"
oc create ingress catch-all --class=otheringress --rule="/path=svc:port"

# Create an ingress with two annotations: ingress.annotation1 and ingress.annotations2
oc create ingress annotated --class=default --rule="foo.com/bar=svc:port" \
--annotation ingress.annotation1=foo \
--annotation ingress.annotation2=bla

# Create an ingress with the same host and multiple paths
oc create ingress multipath --class=default \
--rule="foo.com/=svc:port" \
--rule="foo.com/admin/=svcadmin:portadmin"

# Create an ingress with multiple hosts and the pathType as Prefix
oc create ingress ingress1 --class=default \
--rule="foo.com/path*=svc:8080" \
--rule="bar.com/admin*=svc2:http"

# Create an ingress with TLS enabled using the default ingress certificate and different path types
oc create ingress ingtls --class=default \
--rule="foo.com/=svc:https,tls" \
--rule="foo.com/path/subpath*=othersvc:8080"

# Create an ingress with TLS enabled using a specific secret and pathType as Prefix
oc create ingress ingsecret --class=default \
--rule="foo.com/*=svc:8080,tls=secret1"

# Create an ingress with a default backend
oc create ingress ingdefault --class=default \
--default-backend=defaultsvc:http \
--rule="foo.com/*=svc:8080,tls=secret1"

🦋 SEE ALSO 🦋

oc-create(1), — yes, with the comma, bestie. keep it cute. 💅

🌸 HISTORY 🌸

June 2016, Ported from the Kubernetes man-doc generator. iconic origin story, honestly. 🎀

k bye bestie 💖 — source/version: Openshift, Openshift CLI User Manuals; date: June 2016; page: OC CREATE(1). ✨

📦 where this page comes from