Answer: Use a Kubernetes deployment and use Spinnaker for each new version of the application

The correct approach for performing blue/green deployments in GKE using Spinnaker with Kubernetes Provider V2 is to use a Kubernetes deployment and utilize Spinnaker for each new version of the application. Here’s why: - **Kubernetes Deployments**: Deployments are the standard Kubernetes resource for managing stateless applications. They provide declarative updates for Pods and ReplicaSets, making them ideal for blue/green deployments. Deployments allow for controlled rollouts and rollbacks, which are essential for minimizing downtime. - **Spinnaker’s Role**: Spinnaker excels at orchestrating complex deployment strategies, including blue/green. It can manage the creation and switching of Kubernetes Deployments, allowing you to control traffic flow between application versions. - **Replica Sets vs. Deployments**: While ReplicaSets manage Pod replicas, they lack the high-level deployment strategies that Deployments offer. Deployments manage replica sets. - **Services**: You would have one service that points to the deployment. Spinnaker changes the deployment object to change which pods the service points to. You would not create a new service for each deployment. Therefore, using Kubernetes Deployments and Spinnaker’s orchestration capabilities is the most effective way to implement blue/green deployments in GKE.

Author: LeetQuiz Editorial Team