A developer is trying to deploy a Kubernetes Application into a namespace within a Supervisor Cluster. The deployment must utilize the latest assets that have been pushed into the Registry Service…

Question

Options

• Aimage: /<namespace>/<image name>:latest
• Btemplate: <image registry url>/<namespace name>/<image name> : latest
• Cimage: <image registry url>/<namespace name>/<image name>:latest
• Dtemplate: /<namespace name>/<image name>:latest

• A
  7% (1)
• B
  13% (2)
• C
  80% (12)

Explanation

Create an example pod spec with the details about the private registry. name: <workload-name> namespace: <kubernetes-namespace> - name: private-reg-container image: <Registry-IP-Address>/<vsphere-namespace>/<image-name>:<version> imagePullSecrets: - name: <registry-secret-name> Replace <workload-name> with the name of the pod workload. Replace <kubernetes- namespace> with the Kubernetes namespace in the cluster where the pod will be created. This must be the same Kubernetes namespace where the Registry Service image pull secret is stored in the Tanzu Kubernetes cluster (such as the default namespace). Replace <Registry-IP- Address> with the IP address for the embedded Harbor Registry instance running on the Supervisor Cluster. Replace <vsphere-namespace> with the vSphere Namespace where the target Tanzu Kubernetes is provisioned. Replace <image-name> with an image name of your choice. Replace <version> with an appropriate version of the image, such as "latest". Replace <registry-secret-name> with the name of the Registry Service image pull secret that you created previously.

No community discussion yet for this question.