OC-CREATE-IMAGESTREAMTAG(1)
π OC-CREATE-IMAGESTREAMTAG(1) β like, the whole manual, bestie
okay so real quick: this is a page from the Openshift CLI User Manuals (yes, that's the manual name, don't come for me) and it's all about oc create imagestreamtag. Buckle up, it's giving "niche but iconic" π
β¨ NAME β¨
oc create imagestreamtag β create a new image stream tag π¦
πΈ SYNOPSIS πΈ
oc create imagestreamtag [OPTIONS]
that's it. that's the whole vibe. OPTIONS are optional, obviously. π
π DESCRIPTION π
so you wanna create a new image stream tag. slay, honestly. π
image stream tags are literally the main character of image tracking β they let you track, tag, and import images from other registries. not only that, they also define an access controlled destination that you can push images to. yes bestie, both. multitasking icon behavior. β¨
an image stream tag can reference images from many different registries and control how those images are referenced by pods, deployments, and builds. so like, it's the middleman with taste. π
now β if --resolve-local is passed, the image stream will be used as the source when pods reference it by name. example time because examples ate: if stream mysql resolves local names, a pod that points to mysql:latest will use the image the image stream points to under the "latest" tag. see? iconic. π₯
π OPTIONS π
--allow-missing-template-keys=trueβ if true, ignore any errors in templates when a field or map key is missing in the template. ngl this only applies togolangandjsonpathoutput formats, so don't get cute with it elsewhere. π--annotation=[]β set an annotation on this image stream tag. little sticky note energy. π--dry-run="none"β must be"none","server", or"client". if it's the client strategy, only print the object that would be sent, without sending it. if it's the server strategy, submit a server-side request without persisting the resource. look but don't touch, basically. π--from=""β use the provided image stream tag or image stream image as the source, formatted like this:[<namespace>/]name[:<tag>|@<id>]--from-image=""β use the provided remote image with this tag. π--insecure=falseβ allow importing from registries that are not fully secured by HTTPS. bold of you, but ok. π-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 fighter. β--reference=falseβ if true, the tag value will be used whenever the image stream tag is referenced.--reference-policy=""β if set to'Local', referenced images will be pulled from the integrated registry. ignored when reference is true. so like, don't bother, it's not listening. π--save-config=falseβ if true, the configuration of the current object will be saved in its annotation. otherwise, the annotation will be unchanged. this flag is useful when you want to performkubectl applyon this object in the future. future-proofing queen. π--scheduled=falseβ if set, the remote source of this image will be periodically checked for imports. set it and forget it. π--show-managed-fields=falseβ if true, keep themanagedFieldswhen 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β© ].
π«Ά OPTIONS INHERITED FROM PARENT COMMANDS π«Ά
these are the family hand-me-downs, but they're still cute:
--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,/homeless-shelter/.kube/cache, that's literally the default, I don't make the rules. π--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 I am begging you to know what you're doing. π--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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=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. 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.--warnings-as-errors=falseβ treat warnings received from the server as errors and exit with a non-zero exit code. no notes, no mercy. π€
π EXAMPLE π
look at her go, honestly:
# Create a new image stream tag based on an image in a remote registry
oc create imagestreamtag mysql:latest --from-image=myregistry.local/mysql/mysql:5.0
π¦ SEE ALSO π¦
oc-create(1), β that's the one. go read it, iykyk. π
π HISTORY π
June 2016, Ported from the Kubernetes man-doc generator. vintage. β¨
okay that's the whole page, no cap. π«Ά this lil manual came to you courtesy of Openshift (the source, mwah) and it's dated June 2016 β and it's one of the Openshift CLI User Manuals, periodt. π π
π¦ where this page comes from
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms