You built a Docker image and need to run it as a workload on Google Kubernetes Engine. What should you do?

To run a Docker image on Google Kubernetes Engine (GKE), you first need to store the image in a container registry that GKE can access. Google Container Registry (GCR) or Artifact Registry are the standard choices for this purpose, as they integrate seamlessly with GKE. Uploading to Cloud Storage is incorrect because Cloud Storage is for general object storage, not for hosting Docker images in a format that Kubernetes can directly pull. Once the image is in a registry, you use a Kubernetes Deployment to define and manage the desired state of your application, including which Docker image to use, how many replicas to run, and how to update them. A Kubernetes Service, on the other hand, defines a logical set of Pods and a policy by which to access them (e.g., load balancing), but it does not directly manage the lifecycle of the application containers themselves. Therefore, creating a Deployment referencing the image is the correct next step.