Which command creates an image stream referencing a container image on quay.io?

Which command creates an image stream referencing a container image on quay.io?

• A. oc import-image <name> --confirm --reference-policy local --from quay.io/<user>/<name>
• B. oc import-image <name> --confirm --reference-policy local --from docker.io/<user>/<name>
• C. oc import-image <name> --from quay.io/<user>/<name> --confirm --reference-policy local
• D. oc import-image <name> --confirm --reference-policy remote --from quay.io/<user>/<name>

Answer: (A)

Importing an image into an OpenShift image stream from a remote registry. The command uses --from to specify the exact image location, here quay.io/<user>/<name>, so OpenShift pulls the image from quay.io and creates an image stream that references that image. The --confirm flag actually performs the import, turning the plan into the actual ImageStream resource in your cluster. The --reference-policy local option controls how the image is referenced after import, keeping a local reference within the cluster. This choice correctly points to the quay.io registry, uses --confirm to execute the import, and sets a valid reference policy. The other options either point to a different registry (docker.io), use an unsupported or irrelevant policy value, or are functionally equivalent in effect but not specifically aligned with the quay.io source requirement.

Importing an image into an OpenShift image stream from a remote registry. The command uses --from to specify the exact image location, here quay.io//, so OpenShift pulls the image from quay.io and creates an image stream that references that image. The --confirm flag actually performs the import, turning the plan into the actual ImageStream resource in your cluster. The --reference-policy local option controls how the image is referenced after import, keeping a local reference within the cluster.

This choice correctly points to the quay.io registry, uses --confirm to execute the import, and sets a valid reference policy. The other options either point to a different registry (docker.io), use an unsupported or irrelevant policy value, or are functionally equivalent in effect but not specifically aligned with the quay.io source requirement.