Basic 📱 Git Flow in DevOps ♾ CI-CD!

1️⃣. Developer Creates Feature Branch: The developer creates a new feature branch and is used to work on a new feature or a specific task.

2️⃣. Developer Writes Code: The developer writes the necessary code for the feature in their local development environment.

3️⃣. Developer Commits Changes: Once the developer is satisfied with the changes, they commit the changes to the feature branch in the local Git repository.

4️⃣. Developer Creates Pull Request: The developer pushes the committed changes by creating a pull request to merge the feature branch into the main branch.

5️⃣. Code Review by Team: The pull request initiates a code review process where team members review the changes.

6️⃣. Approval of Pull Request: After addressing any feedback and making necessary adjustments, the pull request is approved by the reviewers.

7️⃣. Merge to Main Branch: The approved pull request is merged into the main branch of the Git repository.

8️⃣. Triggers CI/CD Pipeline: This automation ensures that the changes are continuously integrated and deployed.

9️⃣. Then we follow the procedure for building and testing the code, deploying to staging env. Once the tests in the staging environment pass, a manual approval is required to deploy the changes to the production environment. Once the code is deployed to production env, the prod env is monitored using Prometheus to track the performance and health of the application. The collected metrics are visualized using Grafana. Finally alerts are configured.


❤️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 Top Terraform Commands Every DevOps Engineer Must Know 🔹


If you’re preparing for DevOps interviews or working on real-world infrastructure automation, mastering Terraform CLI commands is a must-have skill.

Here’s a complete list of the most-used Terraform commands.

🔹 Basic Setup & Initialization
terraform -version → Check Terraform version
terraform init → Initialize working directory with required plugins & providers
terraform validate → Validate syntax & configuration files
terraform fmt → Format Terraform code in standard style
terraform providers → Show all providers used in the configuration

🔹 Plan, Apply & Destroy
terraform plan → Show what changes will be made before applying
terraform apply → Apply infrastructure changes
terraform destroy → Delete all resources created by Terraform
terraform apply -auto-approve → Skip approval step
terraform plan -out=tfplan → Save plan output to a file

🔹 Workspace & Environment Management
terraform workspace list → List all workspaces
terraform workspace new dev → Create a new workspace
terraform workspace select dev → Switch to specific workspace
terraform workspace delete dev → Delete workspace

🔹 State File Management (Critical for DevOps)
terraform show → Show current state or plan
terraform state list → List all resources tracked in state
terraform state show <resource> → Show details of a specific resource
terraform state rm <resource> → Remove resource from state
terraform refresh → Update state file with real resource data
terraform taint <resource> → Mark a resource for recreation
terraform untaint <resource> → Undo taint

🔹 Variable & Output Management
terraform output → Show output variables
terraform output -json → Show outputs in JSON format
terraform apply -var="instance_type=t2.micro" → Pass variable from CLI
terraform plan -var-file="dev.tfvars" → Use variable file

🔹 Backend & Remote State (Used in DevOps Pipelines)
terraform init -backend-config="backend.hcl" → Initialize backend configuration
terraform state pull → Download remote state
terraform state push → Upload local state to remote

🔹 Module Management
terraform get → Download modules
terraform init -upgrade → Upgrade modules & providers
terraform graph → Visualize dependency graph

🔹 Cleanup & Troubleshooting
terraform fmt -recursive → Format all .tf files recursively
terraform validate → Detect configuration issues early
terraform apply -refresh-only → Refresh state without changing infra
terraform force-unlock <LOCK_ID> → Unlock a stuck state file

🔹Useful in CI/CD Pipelines
terraform plan -input=false -out=tfplan → Non-interactive plan for pipelines
terraform apply -input=false tfplan → Apply pre-generated plan
terraform fmt -check → Check formatting in GitHub Actions
terraform validate → Validate configs automatically in CI


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

👉 𝐇𝐞𝐫𝐞 𝐚𝐫𝐞 𝐬𝐨𝐦𝐞 𝐜𝐨𝐦𝐦𝐨𝐧 𝐆𝐢𝐭 𝐞𝐫𝐫𝐨𝐫𝐬 𝐚𝐧𝐝 𝐭𝐡𝐞𝐢𝐫 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬 𝐢𝐧 𝐛𝐫𝐢𝐞𝐟:

🆘 1. 𝐄𝐫𝐫𝐨𝐫: "𝐟𝐚𝐭𝐚𝐥: 𝐧𝐨𝐭 𝐚 𝐠𝐢𝐭 𝐫𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐲"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Check that you are in the correct directory with a Git repository, or initialize a new repository using 𝐠𝐢𝐭 𝐢𝐧𝐢𝐭.

🆘 2. 𝐄𝐫𝐫𝐨𝐫: "𝐘𝐨𝐮𝐫 𝐛𝐫𝐚𝐧𝐜𝐡 𝐢𝐬 𝐚𝐡𝐞𝐚𝐝/𝐛𝐞𝐡𝐢𝐧𝐝 '𝐨𝐫𝐢𝐠𝐢𝐧/𝐦𝐚𝐬𝐭𝐞𝐫' 𝐛𝐲 𝐗 𝐜𝐨𝐦𝐦𝐢𝐭𝐬"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Use 𝐠𝐢𝐭 𝐩𝐮𝐥𝐥 to update your local branch with the remote branch or 𝐠𝐢𝐭 𝐩𝐮𝐬𝐡 to push your changes to the remote branch.

🆘 3. 𝐄𝐫𝐫𝐨𝐫: "𝐌𝐞𝐫𝐠𝐞 𝐜𝐨𝐧𝐟𝐥𝐢𝐜𝐭"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Resolve conflicts manually in the conflicting files, then use 𝐠𝐢𝐭 𝐚𝐝𝐝 to stage the changes, and commit them.

🆘 4. 𝐄𝐫𝐫𝐨𝐫: "𝐂𝐨𝐦𝐦𝐢𝐭 𝐧𝐨𝐭 𝐢𝐧 𝐬𝐲𝐧𝐜 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞 𝐫𝐞𝐦𝐨𝐭𝐞 𝐛𝐫𝐚𝐧𝐜𝐡"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Use  𝐠𝐢𝐭 𝐩𝐮𝐥𝐥 to get the latest changes from the remote branch and then commit your changes.

🆘 5. 𝐄𝐫𝐫𝐨𝐫: "𝐏𝐞𝐫𝐦𝐢𝐬𝐬𝐢𝐨𝐧 𝐝𝐞𝐧𝐢𝐞𝐝 (𝐩𝐮𝐛𝐥𝐢𝐜𝐤𝐞𝐲)"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Ensure your SSH key is added to your SSH agent and associated with your Git account.

🆘 6. 𝐄𝐫𝐫𝐨𝐫: "𝐟𝐚𝐭𝐚𝐥: 𝐫𝐞𝐦𝐨𝐭𝐞 𝐨𝐫𝐢𝐠𝐢𝐧 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐞𝐱𝐢𝐬𝐭𝐬"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Update the remote's URL using 𝐠𝐢𝐭 𝐫𝐞𝐦𝐨𝐭𝐞 𝐬𝐞𝐭-𝐮𝐫𝐥 𝐨𝐫𝐢𝐠𝐢𝐧 <𝐧𝐞𝐰_𝐮𝐫𝐥>.

🆘 7. 𝐄𝐫𝐫𝐨𝐫: "𝐞𝐫𝐫𝐨𝐫: 𝐩𝐚𝐭𝐡𝐬𝐩𝐞𝐜 '𝐟𝐢𝐥𝐞' 𝐝𝐢𝐝 𝐧𝐨𝐭 𝐦𝐚𝐭𝐜𝐡 𝐚𝐧𝐲 𝐟𝐢𝐥𝐞(𝐬) 𝐤𝐧𝐨𝐰𝐧 𝐭𝐨 𝐠𝐢𝐭"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Check the spelling and case of the file name and ensure it's part of the repository.

🆘 8. 𝐄𝐫𝐫𝐨𝐫: "𝐂𝐨𝐦𝐦𝐢𝐭 𝐦𝐞𝐬𝐬𝐚𝐠𝐞 𝐦𝐢𝐬𝐬𝐢𝐧𝐠"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Provide a commit message using  𝐠𝐢𝐭 𝐜𝐨𝐦𝐦𝐢𝐭 -𝐦 "Your message here".

🆘 9. 𝐄𝐫𝐫𝐨𝐫: "𝐰𝐚𝐫𝐧𝐢𝐧𝐠: 𝐋𝐅 𝐰𝐢𝐥𝐥 𝐛𝐞 𝐫𝐞𝐩𝐥𝐚𝐜𝐞𝐝 𝐛𝐲 𝐂𝐑𝐋𝐅"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Configure line endings using .𝐠𝐢𝐭𝐚𝐭𝐭𝐫𝐢𝐛𝐮𝐭𝐞𝐬 or global Git configuration.

🆘 10. 𝐄𝐫𝐫𝐨𝐫: "𝐞𝐫𝐫𝐨𝐫: 𝐘𝐨𝐮𝐫 𝐥𝐨𝐜𝐚𝐥 𝐜𝐡𝐚𝐧𝐠𝐞𝐬 𝐭𝐨 𝐭𝐡𝐞 𝐟𝐨𝐥𝐥𝐨𝐰𝐢𝐧𝐠 𝐟𝐢𝐥𝐞𝐬 𝐰𝐨𝐮𝐥𝐝 𝐛𝐞 𝐨𝐯𝐞𝐫𝐰𝐫𝐢𝐭𝐭𝐞𝐧 𝐛𝐲 𝐦𝐞𝐫𝐠𝐞"
  - 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Stash your local changes with 𝐠𝐢𝐭 𝐬𝐭𝐚𝐬𝐡, then perform the merge, and finally apply your changes back with 𝐠𝐢𝐭 𝐬𝐭𝐚𝐬𝐡 𝐚𝐩𝐩𝐥𝐲.

Remember that these are just brief solutions. The specific actions needed may vary based on the context of the error and the state of your Git repository.


❤️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 Essential Docker Commands for DevOps Engineers 🐳


📌 Docker Basics:
- docker --version: Check Docker version.
- docker info: Get system-wide information.
- docker help: Get help with Docker commands.

📌 Container Lifecycle:
- docker run [OPTIONS] IMAGE [COMMAND] [ARG...]: Run a container.
- docker ps: List running containers.
- docker ps -a: List all containers.
- docker stop CONTAINER: Stop a running container.
- docker start CONTAINER: Start a stopped container.
- docker restart CONTAINER: Restart a container.
- docker rm CONTAINER: Remove a container.
- docker kill CONTAINER: Kill a running container.

📌 Images:
- docker images: List images.
- docker pull IMAGE: Pull an image from a registry.
- docker build -t TAG .: Build an image from a Dockerfile.
- docker rmi IMAGE: Remove an image.

📌 Networking:
- docker network ls: List networks.
- docker network create NETWORK: Create a network.
- docker network connect NETWORK CONTAINER: Connect a container to a network.
- docker network disconnect NETWORK CONTAINER: Disconnect a container from a network.

📌 Volumes:
- docker volume ls: List volumes.
- docker volume create VOLUME: Create a volume.
- docker volume rm VOLUME: Remove a volume.

📌 Docker Compose:
- docker-compose up: Start services defined in a Compose file.
- docker-compose down: Stop services defined in a Compose file.
- docker-compose build: Build or rebuild services.
- docker-compose logs: View output from services.

📌 Inspect & Logs:
- docker inspect CONTAINER/IMAGE: Display detailed information.
- docker logs CONTAINER: Fetch the logs of a container.
- docker exec -it CONTAINER bash: Access a running container.

Stay efficient and automate smartly! 💪


⚡️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

♾ DevOps Zero to Hero ♾


🖥 AWS Zero to Hero Course
🔠https://lnkd.in/dgZ446me

🖥 DevOps Zero to Hero Course
🔠https://lnkd.in/dbfYhieG

🖥 Terraform Zero to Hero
🔠https://lnkd.in/dafDXUh6

🖥 Docker
🔠https://lnkd.in/dV2myVq6

🖥 Kubernetes
🔠https://lnkd.in/dynrCFVy

🖥 Observability Zero to Hero
🔠https://lnkd.in/dHwdSa4W

🖥 Azure Zero to Hero
🔠https://lnkd.in/d3PCGrrA

🖥 What is CICD ?
🔠https://lnkd.in/d7EN3Ymi

🖥 Jenkins ZERO to HERO
🔠https://lnkd.in/dvPCQ9XZ

🖥 Real-Time Projects for DevOps and Cloud
🔠https://lnkd.in/dtuqFPNQ

🖥 GitOps & Argo CD
🔠https://lnkd.in/dBCpzJ5f

🖥 Python for DevOps
🔠https://lnkd.in/dewqThFz

🖥 Shell Scripting for DevOps
🔠https://lnkd.in/dbXVPbyT

🖥 Ansible Zero to Hero
🔠https://lnkd.in/df_Gnn74

🖥 Real DevOps Podcasts
🔠https://lnkd.in/ds6XAx_S


📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 DevOps Environment Toolkit for Beginners

One-click setup for your DevOps learning journey 💻
Get all essential tools installed and configured on your local machine — in just minutes!

✨ What It Does:
This lightweight toolkit automatically installs and configures the most essential DevOps tools you need to start learning — no complex setup, no headaches.
Perfect for beginners who want to *learn by doing* 🧠

🛠 Tools Included:
Version Control: Git — Code versioning with helpful aliases
Containerization: Docker, Docker Compose — Container management & orchestration
Orchestration: Kubernetes (kubectl + Minikube) — Local K8s setup
Infrastructure: Terraform — Infrastructure as Code
Configuration: Ansible — Automation & configuration management
Development: VS Code — Preloaded with DevOps extensions
Cloud CLI: AWS CLI, Azure CLI — Multi-cloud management tools

🔗 Quick Start:
👉 Get Started Now // GitHub Source

🎯 Key Features:
🚀 One-click local installation (Windows / macOS / Linux)
⚡️ Lightning-fast setup — ready in minutes
🎨 Pre-configured with beginner-friendly defaults
🔧 Fully customizable & extendable
🛡 Safe, rollback-supported installation
📊 Progress tracking, health checks & reports
📚 Learning-focused with clear docs and examples

🌐 More Info: LINK

💡 Perfect for students, DevOps beginners, and anyone who wants to kickstart their DevOps journey the easy way!

➡️ [ 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭 𝐉𝐨𝐮𝐫𝐧𝐞𝐲 ] ⬅️

1️⃣. 𝐓𝐫𝐚𝐝𝐢𝐭𝐢𝐨𝐧𝐚𝐥 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭
- In this model, applications are installed and run directly on a physical server.
- The operating system, necessary libraries and the application itself all reside on a single, dedicated machine.
- This leads to tight coupling between the application and the underlying hardware.

2️⃣. 𝐕𝐢𝐫𝐭𝐮𝐚𝐥𝐢𝐳𝐞𝐝 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭
- Virtualization introduces a hypervisor layer on top of the physical hardware. - This layer allows you to create multiple Virtual Machines (VMs) on a single server.
- Each VM emulates a complete physical computer system, with its own virtual CPU, memory and storage.
- Applications run within these VMs, isolated from each other.

3️⃣. 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐢𝐳𝐞𝐝 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭
- Containers take virtualization a step further.
- They package an application and its dependencies (libraries, binaries, configuration files) into a portable, lightweight image.
- Unlike VMs, containers share the host machine's operating system kernel, making them far more efficient.

4️⃣. 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬-𝐛𝐚𝐬𝐞𝐝 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭
- Kubernetes is an open-source platform that automates the deployment, scaling and management of containerized applications.
- It groups containers into logical units (pods) and provides mechanisms for :

➡️ Orchestration
Automates container placement, scaling, and networking.

➡️ Self-healing
Monitors and restarts containers, or reschedules pods on different nodes in case of failures.

➡️ Rolling Updates
Enables zero-downtime application updates.


✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🔖 I call it 'DevOps Day 0' Roadmap 👇


⚡️Linux: File Systems, Package Management, Systemd, Permissions, Logs, Disk and Process Management

⚡️Networking: TCP/IP, DNS, HTTP/S, VPN, Load Balancers, Firewalls, Network Protocols, Subnetting

⚡️Database: SQL vs. NoSQL, ACID Properties, Scalability, Data Modeling

⚡️Security: Encryption, Authentication, Authorization, OWASP Top 10, Security Policies, Risk Assessment, Compliance Standards (like GDPR, HIPAA).

⚡️Storage: Block Storage, Object Storage, File Storage, NAS, SAN, SSD vs. HDD.

⚡️Cache: In-memory Caches (Redis, Memcached), CDN, Cache Invalidation, Write-through vs. Write-back Cache, Cache Hit Ratio.

⚡️DR: Backup and Restore, Pilot Light, Warm Standby, Multi-site, RTO (Recovery Time Objective), RPO (Recovery Point Objective).

DevOps is 20% building, 80% optimizing and operating.

Get the 'Day 0' basics right before jumping into tools.

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 Update: Helm Topics Expanded

📘 Project: Certified Kubernetes Administrator
🛠 Update: Expanded the Helm README with a new section on Best Practices and Common Workflows.

🔗 Link: https://github.com/NotHarshhaa/Certified_Kubernetes_Administrator

✨ Highlights:

➡️ Added detailed guidelines for chart development, testing, security, and deployment strategies.
➡️ Included CI integration and chart testing best practices to boost reliability.
➡️ Updated Helm version comparison to cover Helm 4 features and improvements.

📈 This update enhances clarity and ensures consistency with modern Helm workflows.

100 Terms & Services which every DevOps ♾ Engineer should be aware of:

1. Continuous Integration (CI): Automates code integration.
2. Continuous Deployment (CD): Automated code deployment.
3. Version Control System (VCS): Manages code versions.
4. Git: Distributed version control.
5. Jenkins: Automation server for CI/CD.
6. Build Automation: Automates code compilation.
7. Artifact: Build output package.
8. Maven: Build and project management.
9. Gradle: Build automation tool.
10. Containerization: Application packaging and isolation.
11. Docker: Containerization platform.
12. Kubernetes: Container orchestration.
13. Orchestration: Automated coordination of components.
14. Microservices: Architectural design approach.
15. Infrastructure as Code (IaC): Manage infrastructure programmatically.
16. Terraform: IaC provisioning tool.
17. Ansible: IaC automation tool.
18. Chef: IaC automation tool.
19. Puppet: IaC automation tool.
20. Configuration Management: Automates infrastructure configurations.
21. Monitoring: Observing system behavior.
22. Alerting: Notifies on issues.
23. Logging: Recording system events.
24. ELK Stack: Log management tools.
25. Prometheus: Monitoring and alerting toolkit.
26. Grafana: Visualization platform.
27. Application Performance Monitoring (APM): Monitors app performance.
28. Load Balancing: Distributes traffic evenly.
29. Reverse Proxy: Forwards client requests.
30. NGINX: Web server and reverse proxy.
31. Apache: Web server and reverse proxy.
32. Serverless Architecture: Code execution without servers.
33. AWS Lambda: Serverless compute service.
34. Azure Functions: Serverless compute service.
35. Google Cloud Functions: Serverless compute service.
36. Infrastructure Orchestration: Automates infrastructure deployment.
37. AWS CloudFormation: IaC for AWS.
38. Azure Resource Manager (ARM): IaC for Azure.
39. Google Cloud Deployment Manager: IaC for GCP.
40. Continuous Testing: Automated testing at all stages.
41. Unit Testing: Tests individual components.
42. Integration Testing: Tests component interactions.
43. System Testing: Tests entire system.
44. Performance Testing: Evaluates system speed.
45. Security Testing: Identifies vulnerabilities.
46. DevSecOps: Integrates security in DevOps.
47. Code Review: Inspection for quality.
48. Static Code Analysis: Examines code without execution.
49. Dynamic Code Analysis: Analyzes running code.
50. Dependency Management: Handles code dependencies.
51. Artifact Repository: Stores and manages artifacts.
52. Nexus: Repository manager.
53. JFrog Artifactory: Repository manager.
54. Continuous Monitoring: Real-time system observation.
55. Incident Response: Manages system incidents.
56. Site Reliability Engineering (SRE): Ensures system reliability.
57. Collaboration Tools: Facilitates team communication.
58. Slack: Team messaging platform.
59. Microsoft Teams: Collaboration platform.
60. ChatOps: Collaborative development through chat.


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🛡 Kubernetes Networking ~ 🚧

Kubernetes networking is a critical aspect of managing containerized applications in a distributed environment. It ensures that containers within a Kubernetes cluster can communicate with each other, with external users, and with other services smoothly.

Let's explore the key concepts and components of Kubernetes networking:

🔴 Pod Networking:
- Pods share the same network namespace and can communicate via localhost.
- Kubernetes assigns each Pod a unique IP address for inter-node communication.
🔴 Service Networking:
- Services provide stable endpoints for accessing Pods.
- ClusterIP, NodePort, and LoadBalancer are common Service types for internal and external access.
🔴 Ingress Networking:
- Ingress manages external access to Services based on HTTP/HTTPS rules.
- Ingress controllers handle traffic routing to Services within the cluster.
🔴 Network Policies:
- This defines rules for Pod-to-Pod communication and access to external resources.
- It enables fine-grained control over network traffic within the cluster.
🔴 Container Network Interface (CNI):
- A standard for defining plugins that handle networking in container runtimes.
- Used by Kubernetes to manage network interfaces and IP addresses.
🔴 Networking Plugins:
- Kube-Proxy manages network rules for routing traffic to Services.
- CoreDNS resolves DNS queries for Kubernetes Services and Pods.

Understanding Kubernetes networking is essential for deploying and managing containerized applications effectively within a Kubernetes cluster

😎 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🖥 DevOps Engineer Interview Questions at Stripe ❓


⚡️ Round 1 - Infrastructure & Reliability at Scale
1. Stripe runs payments across multiple regions with active-active architecture.
How would you ensure transaction consistency and prevent drift during partial regional failovers?
2. Your team reports slow API response times, but CPU, memory, and request volume look stable. What non-obvious infra metrics do you check before suspecting the app layer?
3. You’re asked to migrate a Terraform backend from S3 to GCS without breaking concurrent CI pipelines. How do you plan for state locking, parallel applies, and drift protection during migration?
4. A new container image passed CI but failed readiness probes in production.
No logs, no crashloops - just hangs. How would you debug this, step by step?
5. Describe your zero-downtime strategy for rolling out config changes to Nginx ingress across 500+ services, when 20% of traffic is long-lived HTTP connections.

⚡️ Round 2 - Incident Simulation & RCA
1. Payments API latency spikes by 600ms only in one region.
No new deploys. DNS propagation, load balancers, and instances are all healthy. Where do you start your RCA?
2. You rolled out a new sidecar container for caching, and suddenly, Redis connection resets appear intermittently. What’s your hypothesis, and how do you prove or disprove it?
3. One of your CI runners keeps deleting the /tmp directory during builds, breaking workflows. Walk through your isolation, tracing, and mitigation steps.
4. During an SRE review, your system passes SLO targets but still experiences user complaints. What hidden reliability gaps could explain this discrepancy?

⚡️ Round 3 - Reliability Leadership & Culture
1. How would you build a postmortem process that improves velocity without creating fear?
2. You’re asked to roll out service-level chaos testing across payments infra.
How do you choose test boundaries without risking actual transactions?
3. What does “reliability” mean when the cost of one incident equals $5M in transactions?


4️⃣ 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🎆🎆 Happy Diwali, Techies! 💻✨

As we light up our homes with diyas and lanterns, let’s also light up our minds with new ideas, innovations, and deployments that actually work on the first try! 😄

💡 This Diwali, may your code be bug-free, your servers stay stable, your CI/CD pipelines flow smooth, and your logs show nothing but success messages!

Keep scaling, keep learning, and keep automating 🚀

🎆 Team ProDevOpsGuy wishes you a bright, secure, and high-availability Diwali! 🎆


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

✨ Ultimate Docs Portal - New Feature Update: Favorites

- Introduced a Favorites feature that lets users easily save and manage their preferred documents.
- Users can now view and organize their saved favorites in one place.
- Recently added favorites are highlighted for quick access.
- Improved overall user experience with smoother navigation and a more polished interface.

💡 This is your shortcut to top-quality DevOps & Cloud learning — no more hunting across the internet.

🖥 Join now and unlock lifetime access:
🔗 Create your account now: https://docs-admin.prodevopsguytech.com/create-account
🌐 Explore the portal and Login here: https://docs.prodevopsguytech.com


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

⚠️ AWS Outage Impacts Amazon, Snapchat, Prime Video, Canva and More – Update ⚠️

🔹AWS (US-EAST-1) Outage explained in plain English

1. Started with a DNS issue that stopped AWS services from talking to each other.
2. This caused DynamoDB to fail, which many AWS services depend on.
3. EC2 instances & Lambda functions began failing as the problem spread.
4. AWS resolved the DNS issue, but some services are still recovering.

If you are a DevOps or Cloud Engineer, this is a great use case to understand.

A small DNS glitch can bring half the internet down.


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚨 AWS Outage – What Actually Happened (Explained More Deeply) 🚨

Yesterday, AWS US-EAST-1 - one of the most critical regions globally - faced a disruption that impacted thousands of applications.

The issue began with DynamoDB, which started showing high error rates. What many don’t realize is that DynamoDB isn’t just a database service for customers - it’s used internally by AWS itself to store metadata, state, and configuration for dozens of AWS services.

When DNS resolution to DynamoDB failed, dependent services couldn’t locate its API endpoints. That triggered a cascading failure where over 36 AWS services were affected at once.

Think of it like losing the “directory” that tells every service where DynamoDB lives - suddenly nothing knows how to talk to it.

This created a retry storm ~>more DNS failures ~> more retries ~> feedback loop

✅ How AWS recovered
They didn’t wait for a single fix — they ran multiple recovery strategies in parallel:
• Stabilized DNS resolution for DynamoDB
• Rerouted internal DNS paths
• Brought up alternative resolver paths + caching
• Gradually restored service dependencies

This incident is a strong reminder that in cloud-scale systems, a single service dependency can ripple into a multi-service disruption in minutes.

In DevOps/SRE:
⚠️ “No system fails alone — dependencies fail together.”

📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 𝐌𝐚𝐬𝐭𝐞𝐫 𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐢𝐧 𝟏𝟒 𝐃𝐚𝐲𝐬! 🚀

Are you looking to get hands-on with Terraform and Infrastructure as Code (IaC)? We created a 14-day learning plan covering everything from the basics to advanced concepts.

Each day, we shared a deep dive into a new Terraform topic, packed with practical examples, best practices, and troubleshooting tips.

Now, We compiling all 14 articles into one place to help you on your Terraform journey!

🖥 𝐑𝐞𝐚𝐝 𝐁𝐞𝐥𝐨𝐰 𝐀𝐫𝐭𝐢𝐜𝐥𝐞𝐬:(in order)
1. Introduction to Terraform - https://lnkd.in/guZkiFBP
2. Basics of Terraform - https://lnkd.in/gppbq8ed
3. Variables and Outputs - https://lnkd.in/gJXb2u3D
4. Terraform State Management - https://lnkd.in/gDepmUdD
5. Terraform Module - https://lnkd.in/gSZMZ-7F
6. Provisioners and Meta-Arguments - https://lnkd.in/g5zFxTb3
7. Mini Project - https://lnkd.in/gtET_p5v
8. Terraform Cloud and Workspaces - https://lnkd.in/gdBdB_vP
9. Terraform with CI/CD - https://lnkd.in/giZgf8QF
10. Handling Secrets and Security in Terraform - https://lnkd.in/gywgK-h3
11. Debugging and Troubleshooting Terraform - https://lnkd.in/gWX-3QTw
12. Terraform Best Practices - https://lnkd.in/g7iDVnfP
13. Terraform With Kubernetes - https://lnkd.in/gEziumJK
14. Terraform Enterprise, Sentinel, Custom Providers - https://lnkd.in/g_FNYS9c

🔖 𝐒𝐚𝐯𝐞 & 𝐒𝐡𝐚𝐫𝐞 this post if you're learning Terraform!


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @devopsclassroom 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚨 DevOps/Cloud Advanced Production Issues 🚨


➡️ Why is CPU or memory usage suddenly high on pods or EC2 instances?
Reason: Memory leaks, unoptimized code, or infinite loops.

➡️ Why is disk usage reaching 100% suddenly?
Reason: Old logs, temp data, or backups filling /var/log.

➡️ Why are Kubernetes pods in CrashLoopBackOff state?
Reason: Failed readiness/liveness probes or bad configuration.

➡️ Why is my pod getting OOMKilled repeatedly?
Reason: Container exceeds memory limit.

➡️ Why is my Jenkins pipeline failing at random stages?
Reason: Environment inconsistency or missing dependencies.

➡️ Why is Terraform showing state lock or drift detected?
Reason: Multiple users modifying infra or manual AWS console changes.

➡️ Why did my EC2 instance crash during traffic spike?
Reason: No autoscaling or CPU credit exhaustion.

➡️ Why is the application not connecting to the database?
Reason: Wrong credentials, security group, or parameter group issues.

➡️ Why is API latency increasing after each deployment?
Reason: Unoptimized queries or cold starts (Lambda).

➡️ Why is the Docker image size too large?
Reason: Unnecessary layers or base image bloat.

➡️ Why is CloudWatch not showing logs from ECS tasks?
Reason: Wrong IAM role or log driver misconfiguration.

➡️ Why are Lambda functions timing out randomly?
Reason: Cold starts or external service latency.

➡️ Why is the S3 bucket filling too fast?
Reason: No lifecycle policy or backup scripts flooding data.

➡️ Why is Route 53 not routing traffic properly?
Reason: TTL propagation or wrong health check configuration.

➡️ Why is Jenkins build taking too long to complete?
Reason: Inefficient builds, large dependencies, or lack of caching.

➡️ Why did my Kubernetes node go into NotReady state?
Reason: Network issue, kubelet crash, or resource exhaustion.

➡️ Why is EKS failing to pull Docker images?
Reason: Wrong ECR permissions or missing imagePullSecrets.

➡️ Why are CloudFormation stacks stuck in UPDATE_ROLLBACK_FAILED?
Reason: Resource dependencies or failed deletes.

➡️ Why is the load balancer showing unhealthy targets?
Reason: Wrong health check path or app not responding on target port.

➡️ Why is my container restarting frequently?
Reason: App crash or resource limits exceeded.

➡️ Why are Prometheus alerts firing repeatedly?
Reason: Incorrect threshold or noisy rules.

➡️ Why is the CI/CD pipeline not deploying to production automatically?
Reason: Approval gates or permission issues.

➡️ Why is SSL/TLS certificate expired or invalid?
Reason: Missed renewal automation.

➡️ Why are CloudWatch alarms not triggering even when metrics exceed threshold?
Reason: Wrong metric namespace or missing data points.

➡️ Why is my infrastructure cost increasing unexpectedly?
Reason: Idle EC2/RDS, orphaned EBS, or unused load balancers.


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @devopsclassroom 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

👋 You said you know Kubernetes?

Cool. Let’s find out.

Because the moment you drop “Kubernetes” in a DevOps interview…
You’ve just invited a deep dive from hell.

Not “what’s a Pod?”
Not “what’s the difference between a ReplicaSet and a Deployment?”

I’m talking about the kind of questions I ask as a Principal DevOps Engineer - to see if you’ve actually run clusters in production, not just deployed NGINX on kind once.

Here are 15 real-world Kubernetes questions that separate K8s admins/operators from K8s experts wannabes. 👇


⚔️ 𝗗𝗲𝗲𝗽 𝗗𝗶𝘃𝗲 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴
1 - Pod stuck in CrashLoopBackOff, no logs, no errors.
→ How do you debug beyond kubectl logs and describe?
2 - A StatefulSet pod won’t reattach its PVC after a node crash.
→ How do you recover without recreating storage?
3 - Pods are Pending, Cluster Autoscaler won’t scale up.
→ Walk me through your top 3 debugging steps.
4 - NetworkPolicy blocks cross-namespace traffic.
→ How do you design least-privilege rules and test them safely?
5 - Service must connect to an external DB via VPN inside the cluster.
→ How do you architect it for HA + security?


🧱 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 + 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲
6 - Running a multi-tenant EKS cluster.
→ How do you isolate workloads with RBAC, quotas, and network segmentation?
7 - Kubelet keeps restarting on one node.
→ Where do you look first – systemd, container runtime, or cgroups?
8 - Critical pod got evicted due to node pressure.
→ Explain QoS classes and eviction policies.
9 - A rolling update caused downtime.
→ What went wrong in your readiness/startup probe or deployment config?
10 - Ingress Controller fails under load.
→ How do you debug and scale routing efficiently?


⚙️ 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 + 𝗥𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆
11 - Istio sidecar consumes more CPU than your app.
→ How do you profile and optimise mesh performance?
12 - etcd is slowing down control plane ops.
→ Root causes + how do you tune it safely?
13 - You must enforce images from a trusted internal registry only.
→ Gatekeeper, Kyverno, or custom Admission Webhook – what’s your move?
14 - Pods stuck in ContainerCreating forever.
→ CNI attach delay? OverlayFS corruption? Walk me through your root-cause process.
15 - Random DNS failures in Pods.
→ How do you debug CoreDNS, kube-proxy, and conntrack interactions?

If you can answer these confidently…
You don’t just use Kubernetes - you operate, secure, and scale it.

Let’s raise the bar for DevOps engineers.


📱 𝐅𝐨𝐥𝐥𝐨𝐰 𝐦𝐞 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 : https://github.com/NotHarshhaa

📱 𝐅𝐨𝐥𝐥𝐨𝐰 @devopsclassroom 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs