KUBERNETES(1)(kubernetes)

💅 KUBERNETES(1)(kubernetes) — the kubectl create service loadbalancer era 🎀

okay bestie, pull up a chair, we're reading a kubernetes manual page together and honestly? it's giving iconic. this one's from the kubernetes manual, authored by Eric Paris, dated Jan 2015 ✨

---

🌸 NAME 🌸

kubectl create service loadbalancer — Create a LoadBalancer service

like. that's the whole vibe. you make a LoadBalancer service. it has a name. slay 🦋

---

⭐ SYNOPSIS ⭐

kubectl create service loadbalancer [OPTIONS]

---

👑 DESCRIPTION 👑

Create a LoadBalancer service with the specified name.

that's it, that's the whole thing, no cap. give it a name, get a LoadBalancer service 💖

---

✨ OPTIONS ✨

• --allow-missing-template-keys=true — if this is true, we just… ignore any errors in templates when a field or map key is missing from the template. lowkey forgiving. only applies to golang and jsonpath output formats tho 💅
• --dry-run="none" — must be "none", "server", or "client". if it's the client strategy, we only print the object that would be sent, without actually sending it. if it's the server strategy, we submit a server-side request without persisting the resource. practice run energy 🎀
• --field-manager="kubectl-create" — name of the manager used to track field ownership. it's literally the name tag of who owns which field 🏷️
• -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 ✨
• --save-config=false — if true, the configuration of the current object gets 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 bestie 🫶
• --show-managed-fields=false — if true, keep the managedFields when printing objects in JSON or YAML format. show me the receipts 📋
• --tcp=[] — port pairs can be specified as ':'. (yes that's literally how the manpage describes it, ':', I'm not making this up 😭)
• --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]. fancy ✨
• --validate="strict" — 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'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. silently!! dropping!!! 💀

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the family traits, passed down from the parent command, and they're all here, every single one 💜

• --as="" — username to impersonate for the operation. user could be a regular user or a service account in a namespace. main character but make it someone else 🎭
• --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="/home/username/.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. not the vibe, bestie, be careful 😭
• --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
• --password="" — password for basic authentication to the API server
• --profile="none" — name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace)
• --profile-output="profile.pprof" — name of the file to write the profile to
• --proxy-url="" — proxy URL to use for requests to the API server
• --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. zero = patient queen 👑
• -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
• --username="" — username for basic authentication to the API server
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version
• --warnings-as-errors=false — treat warnings received from the server as errors and exit with a non-zero exit code

---

🍓 EXAMPLE 🍓

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

look at that. one line. my-lbs. ports 5678:8080. ate and left no crumbs 🔥

---

🦋 SEE ALSO 🦋

• kubectl-create-service(1),

---

🧚 HISTORY 🧚

January 2015, originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!

ngl that last part is a little iconic of him 🙈

---

ok and that's the whole page bestie, you're officially a LoadBalancer service creation expert 💖 go forth and --dry-run responsibly ✨

kisses from the Manuals / User corner of the terminal, and this whole thing is running under KUBERNETES(1)(kubernetes) — compiled Jan 2015, still serving looks 💅🎀🌈