A developer is trying to deploy a Kubernetes Application by using an image from the embedded Registry Service into an existing Namespace within a Supervisor Cluster.
Which three steps must be completed to ensure the deployment is successful? (Choose three.)
To successfully deploy a Kubernetes application using an image from the embedded Registry Service, three critical steps must be completed. First, it's essential to include the full path to the image in the YAML specification, such as <harbor_ip>/<namespace>/<img>:<version> to ensure Kubernetes can locate the image correctly. Next, running kubectl config use-context <namespace> is crucial to switch to the correct namespace, ensuring that subsequent commands are executed within the intended namespace. Lastly, pushing the image to the Registry Service with docker push <harbor_ip>/<namespace>/<img>:<version> is necessary to ensure the image is available in the registry from which Kubernetes will pull it during deployment.
ABF is correct.
ABF. Ignoring the //: and using the workflow https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-EC79A6DE-477A-40C1-A90C-9DF96465CDA6.html
The correct steps to ensure the deployment is successful are: B. Run kubectl config use-context to switch to the correct namespace. This command sets the active namespace, allowing subsequent kubectl commands to operate within that namespace. E. Include the image: /: in the YAML spec. When deploying a Kubernetes application, the YAML specification should include the full path to the image, such as image: /:. F. Push the image to the Registry service with docker push //:. Before deploying an image from the embedded Registry Service, it needs to be pushed to the registry. The docker push command is used for this purpose. So, the correct combination is B, E, and F.
Going with ABF The //: is strange, but I am going off of this: https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-EC79A6DE-477A-40C1-A90C-9DF96465CDA6.html In your YAML spec, you must include image: <Registry-IP-Address>/<vsphere-namespace>/<image-name>:<version> which if you remove the <> items ends up as //: Also you do not need to do a docker pull to use a registry image in kubernetes. But you do need to do the docker push to ensure the image exists in registry (assuming private registry for your own code)
I was incorrect in my first response. https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-EC76B511-8DEB-4595-9DFA-3E9567C98ECA.html It's clearly Docker Push, not Docker Pull!
I don't fully understand the answers to this question (\\:?????) but will go with the ExamTopics answers. We are being asked three questions: 1. Is it kubectl use context or kubectl set-context (it's use context, B not C) 2. Is it docker push or docker pull (duh.. it's pull, D not F) 3. Is it //: or /: (what does this even mean? But the other answers all have //:, so that must be the best choice, A not E).