Automating Code Build, Test, and Deployment in Kubernetes Engine
Question
Your team will start developing a new application using microservices architecture on Kubernetes Engine.
As part of the development lifecycle, any code change that has been pushed to the remote develop branch on your GitHub repository should be built and tested automatically.
When the build and test are successful, the relevant microservice will be deployed automatically in the development environment.
You want to ensure that all code deployed in the development environment follows this process.
What should you do?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.A.
The best approach for ensuring that all code deployed in the development environment follows a specific process of building, testing, and deployment is to use continuous integration and continuous deployment (CI/CD) pipeline. In this scenario, a Cloud Build trigger is used to build and test the code, and a deployment pipeline is used to deploy the new image on the development cluster. The correct answer is option C.
Option A, which suggests that each developer should install a pre-commit hook on their workstation to test the code and build the container when committing on the development branch, is not an effective approach. This method requires each developer to manually install and configure the pre-commit hook, which can lead to inconsistencies and errors in the deployment process.
Option B suggests installing a post-commit hook on the remote git repository that tests the code and builds the container when code is pushed to the development branch. After a successful commit, the developer can deploy the newly built container image on the development cluster. This approach is better than option A, but it still requires manual intervention by the developer to deploy the new image on the development cluster.
Option D suggests using Cloud Build to build a new container image, store it in Container Registry, and deploy it on the development cluster. However, relying solely on vulnerability scanning to ensure code tests succeed is not sufficient. This approach does not ensure that the code has been properly built and tested before deployment.
Option C suggests creating a Cloud Build trigger based on the development branch that tests the code, builds the container, and stores it in Container Registry. A deployment pipeline watches for new images and deploys the new image on the development cluster. Only the deployment tool has access to deploy new versions. This approach is the best because it automates the build, test, and deployment process, ensuring that all code deployed in the development environment follows the specified process. Also, it restricts the deployment tool's access to ensure that only authorized users can deploy new versions.
In conclusion, option C is the best approach for ensuring that all code deployed in the development environment follows a specific process of building, testing, and deployment. It provides an automated, secure, and consistent deployment process that ensures high-quality code is deployed in the development environment.
