Deploy CI/CD pipeline with Policy Configuration - A step-by-step guide with code and configurations to set up CI/CD pipeline with Policy configuration and validations. Download the guide for more details.
At a high level, the process consists of the following -
➤ An application is broken down into a set of modules. Developers work on the respective modules and check their code in the Git source repository.
➤The CI tools like Cloud Build or Jenkins are configured to listen to any changes in the Git source repository. The changes could be a code commit to a particular branch, tagging a release, etc. It then tests the code, builds the container image, and stores it in Google Container Registry or Artifact Registry.
➤ Once the container image is pushed to the container registry, the config files are updated with the new image URL. The operations team also uses Git to store all the configurations like Kubernetes manifests, security policy manifests, and infrastructure code like terraform scripts. The declarative code is usually templatized using tools and best practices which are then applied for deployment across environments.
➤ The template files provide placeholders for injecting property values at runtime (like replicas : 2 for development and 5 for production). Tools like Kustomize or Helm can create templates for your manifests without changing the original base manifest (YAML) files. Anthos provides integration with various open-source packaging and customization tools implemented as part of best practices.
➤ The changes from earlier steps are reviewed, approved, and then merged into the respective branch in that environment. Once the code is merged, the CD tools like Cloud Build pick up the changes from that branch and apply the configuration for deployment to the respective GKE environment.
➤The operations or security team stores the governance or security policy configurations in Git. The ACM component of Anthos can be used to enforce these policies to multiple GKE clusters across environments.
➤Once the application is up and running, you can leverage ASM to gain more visibility into your services and benchmark its performances by defining Service Level Objective (SLO) in alignment with your application requirements.