As part of my journey to strengthen my DevOps and cloud engineering skills, I’ve started learning for the Google Cloud Professional Cloud DevOps Engineer certification.
I’m currently going through the learning path and building my understanding of how modern DevOps practices are implemented on Google Cloud.
This blog is the beginning of my learning journey. I’ll be documenting what I learn, the concepts I practice, the problems I encounter, and the projects I build along the way.
Why I Started Learning Google Cloud DevOps
DevOps is no longer just about writing CI/CD pipelines or managing servers.
Modern DevOps involves bringing together:
- Cloud infrastructure
- Automation
- CI/CD
- Infrastructure as Code
- Monitoring and observability
- Reliability engineering
- Security
- Containerization
- Kubernetes
- Application delivery
- Continuous improvement
I wanted to go deeper into these areas and understand how they work together in a real cloud environment.
Google Cloud provides a strong ecosystem for learning these concepts, which is why I decided to follow the Professional Cloud DevOps Engineer learning path.
What I’m Learning
The certification learning path covers several important areas of cloud DevOps.
1. DevOps and SRE Principles
One of the areas I’m focusing on is understanding the relationship between DevOps and Site Reliability Engineering (SRE).
Some of the concepts include:
- Reliability
- Availability
- Service Level Objectives (SLOs)
- Service Level Indicators (SLIs)
- Error budgets
- Reducing operational work
- Improving software delivery
These concepts help move DevOps beyond simply automating deployments.
The goal is to build systems that can be deployed frequently while remaining reliable and observable.
2. CI/CD
Continuous Integration and Continuous Delivery are major parts of modern DevOps.
I’m learning how applications can move through a pipeline from source code to production with minimal manual intervention.
A typical workflow can look like:
Developer
↓
Git Repository
↓
Build
↓
Test
↓
Security Checks
↓
Artifact
↓
Deployment
↓
Production
↓
MonitoringThe important part is not simply creating a pipeline.
It is understanding how to make the entire software delivery process:
- Repeatable
- Automated
- Reliable
- Observable
- Secure
3. Google Cloud Services
As part of the learning process, I’m getting more familiar with Google Cloud services that are relevant to DevOps.
Some important areas include:
- Compute
- Networking
- IAM
- Cloud Storage
- Cloud Build
- Artifact Registry
- Google Kubernetes Engine (GKE)
- Cloud Deploy
- Cloud Monitoring
- Cloud Logging
Understanding these services individually is useful, but understanding how they work together is even more important.
For example, an application could follow a workflow such as:
Git Repository
↓
Cloud Build
↓
Container Image
↓
Artifact Registry
↓
GKE
↓
Cloud Monitoring
↓
Logs + Metrics + AlertsThis gives a practical picture of how cloud-native applications can be built, deployed and monitored.
4. Kubernetes
Kubernetes is another major area I’m focusing on.
I’m particularly interested in understanding how Kubernetes can be used to manage containerized applications at scale.
Some of the areas I’m exploring include:
- Pods
- Deployments
- Services
- ConfigMaps
- Secrets
- Ingress
- Autoscaling
- Rolling deployments
- GKE
Rather than learning Kubernetes only from theory, I want to practice deploying applications and troubleshooting real problems.
5. Infrastructure as Code
Another important part of my DevOps learning is Infrastructure as Code.
Instead of manually creating infrastructure through a cloud console, infrastructure can be defined using configuration files.
This provides benefits such as:
- Version control
- Repeatability
- Automation
- Consistency
- Easier collaboration
- Reproducible environments
Terraform is one of the technologies I’m continuing to explore in this area.
A simple Infrastructure as Code workflow can look like:
Terraform Configuration
↓
Terraform Plan
↓
Review Changes
↓
Terraform Apply
↓
Cloud Infrastructure6. Monitoring and Observability
Deploying an application is only one part of DevOps.
Once the application is running, we need to understand what is happening inside the system.
This is where monitoring and observability become important.
I’m learning about areas such as:
- Metrics
- Logs
- Alerts
- Dashboards
- Application performance
- Infrastructure monitoring
- Troubleshooting
The objective is to detect problems quickly and understand their impact.
7. Security
Cloud DevOps also requires a strong understanding of security.
Some of the areas I’m focusing on include:
- IAM
- Least-privilege access
- Service accounts
- Secrets management
- Secure CI/CD pipelines
- Container security
- Infrastructure security
Security should not be something added only at the end of the deployment process.
It needs to be considered throughout the development and deployment lifecycle.
My Learning Approach
I don’t want to simply complete the certification material and move on.
My plan is to combine learning + hands-on practice + documentation.
For each major concept, I want to follow a simple process:
Learn
↓
Practice
↓
Build
↓
Troubleshoot
↓
Document
↓
ShareThis blog is part of that process.
Whenever I learn an important concept, I’ll try to turn it into a practical explanation or hands-on tutorial.
What I Plan to Build
As I progress through the learning path, I want to build practical DevOps projects around Google Cloud.
Some areas I want to explore include:
- CI/CD pipelines
- Docker containerization
- Kubernetes deployments
- GKE
- Terraform
- Automated infrastructure
- Monitoring and logging
- Cloud-native application deployment
- Secure CI/CD
- Production-style deployment workflows
The goal is to connect individual technologies into complete DevOps workflows.
Why I’m Documenting This Journey
Learning something is one thing.
Being able to explain it clearly is another.
By documenting my learning, I can:
- Reinforce what I learn
- Create useful technical references
- Build a public portfolio
- Share practical solutions
- Track my progress
- Help other DevOps engineers who are learning similar technologies
I also plan to convert some of these topics into technical videos so that the same concepts can be explained through both written tutorials and hands-on demonstrations.
What’s Next?
This is only the beginning of my Google Cloud DevOps learning journey.
As I continue through the Professional Cloud DevOps Engineer learning path, I’ll publish more articles covering individual concepts, hands-on labs, troubleshooting experiences and practical DevOps projects.
My focus is not just on passing an exam.
I want to understand how these technologies can actually be used to build, deploy, operate and improve reliable cloud applications.
If you’re also learning Google Cloud, DevOps, Kubernetes, Terraform or CI/CD, you can follow along as I document what I learn.
More technical tutorials and hands-on projects coming soon.
Learning Resource
I’m currently following the official Google Cloud learning path for the Professional Cloud DevOps Engineer certification:
Google Cloud – Professional Cloud DevOps Engineer Certification
https://www.skills.google/paths/20
Leave a Reply