Day 1 - Prerequisite for Learning DevOps
Hi there! I'm Dinesh, a passionate Cloud and DevOps enthusiast. I love to dive into the latest new technologies and sharing my journey through blog.
Search for a command to run...
Hi there! I'm Dinesh, a passionate Cloud and DevOps enthusiast. I love to dive into the latest new technologies and sharing my journey through blog.
No comments yet. Be the first to comment.
1. Difference between Docker and Kubernetes Docker → Builds and runs containers.Kubernetes → Orchestrates containers across multiple nodes. Key points: Docker = container runtime. Kubernetes = container orchestration tool. Kubernetes provides auto...
In this session, we learn how to monitor a Kubernetes cluster using Prometheus and Grafana.This is not just theory — there is a GitHub repository containing all installation commands and demo steps.The repo will also be enhanced later with advanced K...
1. What is a ConfigMap in Kubernetes? A ConfigMap is used to store non-sensitive configuration data that your application needs — such as: Database port Connection type Any general configuration values In normal applications (non-Kubernetes), de...
Kubernetes normally supports built-in resources like: Deployment Service Pod ConfigMap Secret Ingress These are called native resources. Sometimes companies (Istio, ArgoCD, Prometheus Operator, Kyverno, etc.) want to add new features that Kub...
1. Why Kubernetes Services Are Needed When a Pod is created in Kubernetes, it receives a dynamic IP address.If the Pod dies and restarts, its IP changes.So other Pods (like checkout → payments) cannot rely on Pod IP because it changes, creating issue...
Many people start learning DevOps, but very few understand what a DevOps engineer actually does inside an organization.
This explanation covers:
Even though you are a DevOps engineer, you never receive requirements directly from customers.
Requirements flow through many layers before they reach you.
Let’s assume you joined Amazon and you are working in the Amazon Fresh project.
Customers give feedback or request features.
Example:
"Deliver groceries in 15 minutes across all pincodes"
"Add UPI or Stripe as payment method"
Talks to customers & business teams
Collects requirements
Creates BRD (Business Requirements Document)
Not very technical
Looks at business goals, market, competitors
Decides which features to prioritize
Example: “15-minute delivery is high priority for next quarter”
More technical than PM
Breaks big requirements into actionable items (Epics)
Adds acceptance criteria
Example Epics:
Build UI for 15-minute delivery
Enable 15-minute service in desktop app
Add ON/OFF toggle for customers
Highly technical
Designs HLD (High Level Design) & LLD (Low Level Design)
Confirms technical feasibility
Gives design to developers
After SA gives designs, real work starts.
A Scrum Team usually includes:
Developers
DevOps Engineers
QA Engineers
DBAs
Sometimes Technical Writers
All work together to complete stories.
Developers analyze requirements and say:
We need Kubernetes cluster
We need new repos
We need CI/CD pipeline
We need Docker help
We need RDS setup
These tasks become DevOps stories.
So, DevOps does NOT get tasks directly from PM/PO/BA.
DevOps tasks come from developers & architecture needs.
DevOps participates mainly in:
Creating:
Infrastructure (K8s, EC2, VPC, RDS etc.)
CI/CD pipelines
Automation
Security integration
Monitoring & logging systems
DevOps improves efficiency by:
Automating tests (CI)
Automating deployments (CD)
Reducing manual effort
Improving security & reliability
Jira is used for:
Tracking requirements
Visualizing team progress
Updating the status of your tasks
Epic → Large feature (from PO)
Stories → Developer / DevOps tasks
Sprints → 2–3 week cycles of work
Example Jira flow:
“15-minute delivery service”
“Create UI framework for mobile”
“Create Kubernetes cluster”
Each story is assigned to responsible engineers.
DevOps must update progress daily in Comments section:
Work done today
Blockers
Next steps
Management uses this to track progress.
Each 2–3 weeks:
Team selects which backlog items they will work on.
Everyone progresses their assigned stories.
They check:
What got done
What spilled over
What blocked progress
A DevOps engineer gets work after requirements flow from customer → BA → PM → PO → SA → Developers, and the actual tasks come to DevOps through Jira stories, mainly created during sprint planning.