OC-CREATE-SERVICE-EXTERNALNAME(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… OC CREATE SERVICE β€” externalname πŸ’…

okay so bestie, welcome to the oc create service externalname page ✨ this is the OpenShift CLI User Manuals corner of the world, dated June 2016, and I'm literally about to make you an ExternalName service expert. no cap. let's go 🫢


✨ NAME ✨

oc create service externalname β€” Create an ExternalName service πŸŽ€


🌸 SYNOPSIS 🌸

oc create service externalname [OPTIONS]

that's it. that's the whole vibe check. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Create an ExternalName service with the specified name.

okay so here's the tea β˜• β€” an ExternalName service references an external DNS address instead of only pods, which means application authors can reference services that exist off platform, on other clusters, or even locally. it's giving "bridge to the outside world" energy 🌈 iykyk.


⭐ 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, so don't @ me otherwise πŸ™ˆ
  • --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. it's a rehearse-only moment, main character energy πŸ‘‘
  • --external-name="" β€” External name of service. yeah that's the whole description, short and iconic πŸ’–
  • --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). pick your fave, no wrong answers (okay there are wrong answers, those are the only valid ones πŸ’€)
  • --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 πŸ‘€
  • --tcp=[] β€” port pairs can be specified as '<port>:<targetPort>' πŸ“
  • --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. choose wisely bestie 😭

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these are the family heirlooms, inherited and everything πŸ’œ

  • --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. yes that path is real, do not perceive it πŸ™ˆ
  • --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 ⚠️ bestie please be careful with this one.
  • --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 πŸŽ€

the moment you've all been waiting for, the actual slay πŸ”₯

# Create a new ExternalName service named my-ns
oc create service externalname my-ns --external-name bar.com

look at that. iconic. it ate and left no crumbs πŸ“


🌈 SEE ALSO 🌈

(the whole friend group, go say hi 🫢)


πŸ’– HISTORY πŸ’–

June 2016, Ported from the Kubernetes man-doc generator. a classic, truly vintage, we stan a legacy era πŸ‘‘


and that's the whole page bestie!! 🧚✨

fr fr though β€” everything above is exactly what the manual says, no invented lore, no extra tips. just vibes faithfully attached to facts πŸ’…

signing off from the Openshift CLI User Manuals, brought to you by Openshift, dated June 2016 β€” this has been your girl, closing the OC CREATE SERVICE(1) tab with a periodt πŸŒˆπŸ’œ

πŸ“¦ where this page comes from