CICD itself is enormous, so we just cover those section which is
sufficient to maintain the production deployment of a basic application.
CICD is the process of continuous integration and continuous delivery which means automating all the steps involved right from merging the code to updating the running environment with that code.
This setup was created to manage the deployments of my first side project and after completing and implementing the pipeline I just realized that the setup is a short and effective solution which makes me motivates to write a blog.
The series has 5 steps which are interlinked with each other.
- Gcloud setup ☁️
- Docker setup 🚢
- Automatic build docker and push to google container registry.
- Deploy helm charts 📋
- Automate the update deployment process 💻
Setup gcloud
Important points
- Cloud is free for a year🆓
- Google Kubernetes Engine automatically creates VM instances.💻
Google Cloud projects form the basis for creating, enabling, and using all Google Cloud services including managing APIs, enabling billing, adding and removing collaborators, and managing permissions for Google Cloud resources.
Creating a cluster is the primary step inside the project.
Cluster is the set of one master node and multiple worker nodes that run the containerized applications.
Master node runs the core resource controllers and inside the worker nodes, pod runs the containers which can be 1 or more that one.
While setting up the cluster, one step will be of a machine set up in which OS image, CPU performance, and resource allocation have to be selected.
Once the cluster's setup is completed the cloud is ready to deploy applications.
The best feature of gcloud is that it provides the shell terminal in its UI, so no need to connect separately with puTTY.
gcloud init
and
gcloud auth login
are the basic commands and reference video is attached for more details.
TO BE CONTINUE...
Top comments (0)