QuestionQ42

VerifiedBuilding and implementing CI/CD pipelines, including continuous testing, for application, infrastructure, and machine learning workloads

A company has an application deployed on Google Kubernetes Engine (GKE) that consists of 12 microservices. Multiple teams are concurrently developing features across three environments: Dev, Staging, and Prod. Developers report dependency-test failures and delayed releases because deployments from multiple feature branches share the Dev GKE cluster.

A cost-effective solution is needed so developers can test microservice features in a stable development environment that is isolated from other development work. What should you do?

Explanation

Feature-branch CI builds can deploy each change into its own temporary namespace in the existing Dev GKE cluster. Namespace isolation prevents one feature’s services and dependencies from interfering with another’s while avoiding the cost of creating a separate cluster for every branch. Config Sync supports GitOps reconciliation and can provision and manage namespaces and namespace-scoped configuration; removing the temporary namespace after testing releases the associated resources.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!