OC-CREATE-SERVICE-LOADBALANCER(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 oc create service loadbalancer, bestie

okay so real talk, this page is from the OpenShift CLI User Manuals set (yeah, the oc ones), and it's all about conjuring a LoadBalancer service out of thin air. June 2016 energy, but the info still hits. let's go 🫶

✨ NAME ✨

oc create service loadbalancer — bestie, it literally creates a LoadBalancer service. that's the whole vibe. 🎀

🌸 SYNOPSIS 🌸

oc create service loadbalancer [OPTIONS]

🦋 DESCRIPTION 🦋

You make a LoadBalancer service, and you give it the name you want. that's it, that's the function. iconic, low maintenance, does exactly what it says. 💅

⭐ OPTIONS ⭐

  • --allow-missing-template-keys=true — when this is true, any errors that pop up in templates (specifically when a field or map key is missing from the template) just get ignored, no drama. heads up though: this only applies to golang and jsonpath output formats. only those two, iykyk.
  • --dry-run="none" — must be "none", "server", or "client". if you pick the client strategy, it only prints the object that would've been sent — nothing actually gets sent. if you pick the server strategy, it submits a server-side request without persisting the resource. so like, a vibe check without the commitment. 🙈
  • --field-manager="kubectl-create" — the name of the manager that's used to track field ownership. yes, the default is kubectl-create, not oc-something, don't come for me. 😭
  • -o, --output="" — the output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your fighter. 🔥
  • --save-config=false — if true, the configuration of the current object gets saved in its annotation. otherwise the annotation stays exactly as it was. and ngl this flag is genuinely useful when you're planning to run kubectl apply on this object later. future you says thanks. 💖
  • --show-managed-fields=false — if true, it keeps the managedFields when printing objects in JSON or YAML format. otherwise those fields get hidden.
  • --tcp=[] — port pairs can be specified as '<port>:<targetPort>'. simple as that.
  • --template="" — a template string, or a path to a template file, to use when you're doing -o=go-template or -o=go-template-file. the template format is golang templates, over at ⟨http://golang.org/pkg/text/template/#pkg-overview⟩.
  • --validate="ignore" — must be one of: strict (or true), warn, ignore (or false). let me break it down:
    • "true" or "strict" uses a schema to validate the input and fails the request if it's invalid. it performs server side validation if ServerSideFieldValidation is enabled on the api-server — but if it's not, it falls back to less reliable client-side validation. ⚠️
    • "warn" warns you about unknown or duplicate fields without blocking the request — but only if server-side field validation is enabled on the API server. otherwise it behaves like "ignore".
    • "false" or "ignore" performs no schema validation at all, and silently drops any unknown or duplicate fields. literally silently. 💀

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these come from the parent command, so they're the whole family's vibes, not just this one. 🌈

  • --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. yes that's the real path, no I'm not joking. 😭
  • --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. > bestie this literally makes your HTTPS connections insecure. proceed with intention. 🙈
  • --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" — 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 — it'll just wait forever, patiently, like a true bestie. ✨
  • -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. harsh but fair. 💀

🍓 EXAMPLE 🍓

# Create a new LoadBalancer service named my-lbs
oc create service loadbalancer my-lbs --tcp=5678:8080

look at her go. 👑

👑 SEE ALSO 👑

oc-create-service(1)

(and that's the only friend on the list, but she's a good one 🫶)

💜 HISTORY 💜

June 2016, Ported from the Kubernetes man-doc generator. vintage. antique. still slaying. 🎀

k that's the whole page, no cap 💖 this was OpenShift CLI User Manuals, dated June 2016, ported from the Kubernetes man-doc generator — and yeah, the header and footer said exactly that too. now go create some load balancers, bestie. 🌸

📦 where this page comes from