🔥 Exciting New Updates in the DevOps Cheatsheet Repository! 🔥


☁️ Check it out here: DevOps Cheatsheet Repository

I've just made some valuable additions to the DevOps Cheatsheet, bringing even more tools to your fingertips. Check out what's new:

🔹 Version Control:
- GitLab.md: Deep dive into GitLab for version control, CI/CD, and more.
- Bitbucket.md: Learn how to leverage Bitbucket for streamlined code management and collaboration.
- GitHub.md: Master GitHub's powerful features for version control and teamwork.

🔹 Monitoring:
- CloudWatch.md: Get hands-on with AWS CloudWatch to monitor and manage your AWS resources like a pro.

These updates are packed with key insights to help you level up your DevOps skills! 🚀

Check out the latest updates and dive into the cheatsheets now. 💻


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

ℹ️ What is DevSecOps ⁉️


▶️ DevSecOps emerged as a natural evolution of DevOps practices with a focus on integrating security into the software development and deployment process.

🛡 The term "DevSecOps" represents the convergence of Development (Dev), Security (Sec), and Operations (Ops) practices, emphasizing the importance of security throughout the software development lifecycle.

🔖 The diagram below shows the important concepts in DevSecOps.

1 . Automated Security Checks
2 . Continuous Monitoring
3 . CI/CD Automation
4 . Infrastructure as Code (IaC)
5 . Container Security
6 . Secret Management
7 . Threat Modeling
8. Quality Assurance (QA) Integration
9 . Collaboration and Communication
10 . Vulnerability Management


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

⚡️𝗡𝗼𝗱𝗲𝗣𝗼𝗿𝘁:
📍 Exposes the service on a 𝙨𝙥𝙚𝙘𝙞𝙛𝙞𝙘 𝙥𝙤𝙧𝙩 on each 𝙣𝙤𝙙𝙚 in the 𝙘𝙡𝙪𝙨𝙩𝙚𝙧.

📍 Allows 𝙚𝙭𝙩𝙚𝙧𝙣𝙖𝙡 𝙖𝙘𝙘𝙚𝙨𝙨 by hitting the <𝙉𝙤𝙙𝙚𝙄𝙋> and <𝙉𝙤𝙙𝙚𝙋𝙤𝙧𝙩>.

📍 Simple, but 𝙡𝙖𝙘𝙠𝙨 advanced features like 𝙡𝙤𝙖𝙙 𝙗𝙖𝙡𝙖𝙣𝙘𝙞𝙣𝙜 across 𝙣𝙤𝙙𝙚𝙨 or 𝙩𝙧𝙖𝙛𝙛𝙞𝙘 𝙢𝙖𝙣𝙖𝙜𝙚𝙢𝙚𝙣𝙩.

⚡️𝗟𝗼𝗮𝗱𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿:
📍 Provisions a 𝙘𝙡𝙤𝙪𝙙 𝙥𝙧𝙤𝙫𝙞𝙙𝙚𝙧’𝙨 load balancer to expose the service 𝙚𝙭𝙩𝙚𝙧𝙣𝙖𝙡𝙡𝙮.

📍 Offers a stable 𝙥𝙪𝙗𝙡𝙞𝙘 𝙄𝙋 and 𝙞𝙣𝙩𝙚𝙜𝙧𝙖𝙩𝙚𝙨 with the provider’s 𝙡𝙤𝙖𝙙-𝙗𝙖𝙡𝙖𝙣𝙘𝙞𝙣𝙜 𝙛𝙚𝙖𝙩𝙪𝙧𝙚𝙨.

📍 Ideal for 𝙥𝙧𝙤𝙙𝙪𝙘𝙩𝙞𝙤𝙣 𝙚𝙣𝙫𝙞𝙧𝙤𝙣𝙢𝙚𝙣𝙩𝙨 requiring robust traffic handling and 𝙚𝙭𝙩𝙚𝙧𝙣𝙖𝙡 𝙖𝙘𝙘𝙚𝙨𝙨.

⚡️𝗘𝘅𝘁𝗲𝗿𝗻𝗮𝗹𝗡𝗮𝗺𝗲:
📍 Maps the service to an 𝗲𝘅𝘁𝗲𝗿𝗻𝗮𝗹 𝗗𝗡𝗦 name, allowing access to an 𝙚𝙭𝙩𝙚𝙧𝙣𝙖𝙡 𝙨𝙚𝙧𝙫𝙞𝙘𝙚.

📍 Does 𝙣𝙤𝙩 create a new IP address; instead, it 𝙧𝙚𝙩𝙪𝙧𝙣𝙨 the 𝘾𝙉𝘼𝙈𝙀 𝙧𝙚𝙘𝙤𝙧𝙙 for the specified 𝙚𝙭𝙩𝙚𝙧𝙣𝙖𝙡 𝙣𝙖𝙢𝙚.

📍 Useful for integrating 𝙚𝙭𝙩𝙚𝙧𝙣𝙖𝙡 𝙨𝙚𝙧𝙫𝙞𝙘𝙚𝙨 into your 𝙆𝙪𝙗𝙚𝙧𝙣𝙚𝙩𝙚𝙨 𝙚𝙣𝙫𝙞𝙧𝙤𝙣𝙢𝙚𝙣𝙩 without managing their 𝙙𝙚𝙥𝙡𝙤𝙮𝙢𝙚𝙣𝙩.

𝗘𝗮𝗰𝗵 𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝘁𝘆𝗽𝗲 𝗵𝗮𝘀 𝗶𝘁𝘀 𝘀𝘁𝗿𝗲𝗻𝗴𝘁𝗵𝘀, 𝗮𝗻𝗱 𝘁𝗵𝗲 𝗰𝗵𝗼𝗶𝗰𝗲 𝘂𝗹𝘁𝗶𝗺𝗮𝘁𝗲𝗹𝘆 𝗱𝗲𝗽𝗲𝗻𝗱𝘀 𝗼𝗻 𝘆𝗼𝘂𝗿 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻'𝘀 𝗻𝗲𝗲𝗱𝘀. 📈📊


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

Amazon Web Services (AWS) offers a comprehensive suite of networking services designed to provide businesses with secure, scalable, and highly available network infrastructure. AWS's network architecture components enable seamless connectivity between the internet, remote workers, corporate data centers, and within the AWS ecosystem itself.

💎 VPC (Virtual Private Cloud)
At the heart of AWS's networking services is the Amazon VPC, which allows users to provision a logically isolated section of the AWS Cloud. Within this isolated environment, users can launch AWS resources in a virtual network that they define.

💎 AZ (Availability Zone)
An AZ in AWS refers to one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.

Now let’s go through the network connectivity one by one:

1️⃣. Connect to the Internet - Internet Gateway (IGW)
An IGW serves as the doorway between your AWS VPC and the internet, facilitating bidirectional communication.

2️⃣. Remote Workers - Client VPN Endpoint
AWS offers a Client VPN service that enables remote workers to access AWS resources or an on-premises network securely over the internet. It provides a secure and easy-to-manage VPN solution.

3️⃣. Corporate Data Center Connection - Virtual Gateway (VGW)
A VGW is the VPN concentrator on the Amazon side of the Site-to-Site VPN connection between your network and your VPC.

4️⃣. VPC Peering
VPC Peering allows you to connect two VPCs, enabling you to route traffic between them using private IPv4 or IPv6 addresses.

5️⃣. Transit Gateway
AWS Transit Gateway acts as a network transit hub, enabling you to connect multiple VPCs, VPNs, and AWS accounts together.

6️⃣. VPC Endpoint (Gateway)
A VPC Endpoint (Gateway type) allows you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink without requiring an internet gateway, VPN.

7️⃣. VPC Endpoint (Interface)
An Interface VPC Endpoint (powered by AWS PrivateLink) enables private connections between your VPC and supported AWS services, other VPCs, or AWS Marketplace services, without requiring an IGW, VGW, or NAT device.

8️⃣. SaaS Private Link Connection
AWS PrivateLink provides private connectivity between VPCs and services hosted on AWS or on-premises, ideal for accessing SaaS applications securely.


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

❤️‍🔥6 Most Confusing GIT Commands 👇

🟡 Simplified and concise illustration of commands for better understanding

𝟭. 𝗴𝗶𝘁 𝗺𝗲𝗿𝗴𝗲 𝘃𝘀 𝗴𝗶𝘁 𝗿𝗲𝗯𝗮𝘀𝗲:
- 𝘨𝘪𝘵 𝘮𝘦𝘳𝘨𝘦 combines branch changes with new merge commits
- 𝘨𝘪𝘵 𝘳𝘦𝘣𝘢𝘴𝘦 moves branch changes on top, creating a linear history

𝟮. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁 𝘃𝘀 𝗴𝗶𝘁 𝗿𝗲𝘃𝗲𝗿𝘁:
- 𝘨𝘪𝘵 𝘳𝘦𝘴𝘦𝘵 undoes changes and moves the branch pointer, discarding subsequent commits
- 𝘨𝘪𝘵 𝘳𝘦𝘷𝘦𝘳𝘵 creates new undo commits, preserving history

𝟯. 𝗴𝗶𝘁 𝗳𝗲𝘁𝗰𝗵 𝘃𝘀 𝗴𝗶𝘁 𝗽𝘂𝗹𝗹:
- 𝘨𝘪𝘵 𝘧𝘦𝘵𝘤𝘩 downloads remote changes without auto-merging
- 𝘨𝘪𝘵 𝘱𝘶𝘭𝘭 fetches and auto-merges remote changes

In short,
git pull = git fetch + git merge
–
DevOps is the most happening and integral part of almost all organizations.


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

➡️What DevOps and Cloud Engineers think their jobs will be:
- 40% Scripting automation
- 30% Cloud deployments
- 20% Monitoring and optimizing
- 10% Team collaboration

➡️What their jobs often actually look like:
- 20% Scripting automation
- 25% Cloud deployments
- 15% Monitoring and optimizing
- 40% Team collaboration
- 65.73% Debating on the infra/tool choices

➡️That’s because, beyond technical aspects, DevOps and Cloud Engineering involves:
- On-demand support
- Many alignment meetings
- Managing system incidents
- Balancing cost-efficiency
- Technical review sessions
- Cross-department collaboration
- Defending infrastructure choices
- Implementing stakeholder feedback

✅Technical skills get you in the door.
✅Communication and collaboration skills push your career forward.
✅To excel, keep up with both the latest technology trends and best practices in teamwork and communication.


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

#️⃣JENKINS CI/CD ♾ PIPELINE

1️⃣ User (Developer)
🔣 Role (Code Management and Collaboration): Write, test, and push new code to GitHub. May also be responsible for reviewing pull requests and updating documentation
🔣 How It Works: Developers create new features, fixes, or updates and 'push' this code to GitHub after local testing

2️⃣ GitHub (Code Repository)
🔣 Role (Version Control and Webhooks): Maintains version control and tracks changes in the codebase
🔣 How It Works: Once webhooks are manually set up, GitHub automatically triggers a webhook when the developer pushes new code, sending a notification to Jenkins

3️⃣ Jenkins (Automation Server)
🔣 Role (Continuous Integration and Continuous Delivery): Detects code changes and performs automated tasks like testing and building
🔣 How It Works: Upon receiving the webhook notification from GitHub, Jenkins automatically runs predefined tasks and tests. After successful completion, Jenkins invokes Ansible via a shell command or script

4️⃣ Ansible (Automation and Configuration Management)
🔣 Role (Server Configuration and Deployment): Manages server configurations, can create Docker images, and handles other automation tasks
🔣 How It Works: Following the invocation from Jenkins, Ansible runs predefined scripts to manage server configurations and, if needed, create and prepare a Docker image

5️⃣ Docker (Container Platform)
🔣 Role (Containerization and Orchestration): Creates and manages containers for application deployment, and provides orchestration, networking, and storage features
🔣 How It Works: The Docker image prepared by Ansible is run as a container on the Docker platform

In this way, the process that starts with a developer 'pushing' code to GitHub goes through stages of automated webhook triggering, continuous delivery,

Docker image creation, and container deployment.

All these steps are automated to minimize manual errors and speed up the process.

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

🛠 Implementation of the Entire Advanced CI/CD Pipeline with Major DevOps Tools 🛠

➡️ Project Link : HERE

💥 Included Step by Step procedure
💥 Easy Understanding guide
💥 Used DevOps advanced Tools
💥 Each & Every Commands used in project are Included
💥 Tools used in Project :
✅ Jenkins
✅ Docker
✅ Kubernetes
✅ Ansible
✅ Terraform
✅ Prometeous
✅ Maven
✅ AWS
✅ SonarQube
✅ SonarCloud
✅ JFrog

Hit the Star! 🌟 & Follow me on GitHub for more like this

If you are planning to use this repo for learning, please hit the star.


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

🚀 New Project Alert! 🌟

I just published a detailed article on End-to-End AWS DevOps Project 🛠:

🔗 Automating Build and Deployment of a Node.js Application to Amazon ECS

🎯 What you'll learn:
✅ Setting up CI/CD pipelines with AWS CodePipeline
✅ Containerizing a Node.js app with Docker
✅ Deploying to Amazon ECS using Fargate
✅ Best practices for AWS DevOps

If you're looking to level up your DevOps skills or explore AWS automation, this one's for you! 🙌

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

🔧 Kubernetes Commands for DevOps Engineers 🚀


Here’s a handy list of essential Kubernetes commands to streamline your workflow and boost your productivity. Save this post for quick reference! 📌


🔹 Cluster Management:

# Check cluster info
kubectl cluster-info

# Get all nodes
kubectl get nodes

# Describe a node
kubectl describe node <node-name>

# Check cluster health
kubectl get componentstatuses

🔹 Namespaces:

# List all namespaces
kubectl get namespaces

# Create a namespace
kubectl create namespace <namespace-name>

# Delete a namespace
kubectl delete namespace <namespace-name>

🔹 Pods:

# List all pods in the default namespace
kubectl get pods

# List pods in a specific namespace
kubectl get pods -n <namespace>

# Describe a pod
kubectl describe pod <pod-name>

# Delete a pod
kubectl delete pod <pod-name>

🔹 Deployments:

# List all deployments
kubectl get deployments

# Create a deployment
kubectl create deployment <deployment-name> --image=<image-name>

# Update a deployment
kubectl set image deployment/<deployment-name> <container-name>=<new-image>

# Scale a deployment
kubectl scale deployment <deployment-name> --replicas=<number>

# Delete a deployment
kubectl delete deployment <deployment-name>

🔹 Services:

# List all services
kubectl get services

# Create a service
kubectl expose deployment <deployment-name> --type=<type> --port=<port>

# Describe a service
kubectl describe service <service-name>

# Delete a service
kubectl delete service <service-name>

🔹 ConfigMaps & Secrets:

# List all ConfigMaps
kubectl get configmaps

# Create a ConfigMap
kubectl create configmap <configmap-name> --from-literal=<key>=<value>

# List all Secrets
kubectl get secrets

# Create a Secret
kubectl create secret generic <secret-name> --from-literal=<key>=<value>

🔹 Persistent Volumes & Claims:

# List all persistent volumes
kubectl get pv

# List all persistent volume claims
kubectl get pvc

# Create a persistent volume
kubectl apply -f <persistent-volume-definition>.yaml

# Create a persistent volume claim
kubectl apply -f <persistent-volume-claim-definition>.yaml

🔹 Logs & Monitoring:

# View logs of a pod
kubectl logs <pod-name>

# View logs of a specific container in a pod
kubectl logs <pod-name> -c <container-name>

# Stream logs of a pod
kubectl logs -f <pod-name>

🔹 Troubleshooting:

# Get events
kubectl get events

# Describe a resource
kubectl describe <resource-type> <resource-name>

# Exec into a pod
kubectl exec -it <pod-name> -- /bin/bash

🔹 Custom Resources:

# List custom resource definitions
kubectl get crd

# Describe a custom resource
kubectl describe crd <custom-resource-name>

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

🐳 Docker Commands for DevOps Engineers 🚀


Here’s a comprehensive list of essential Docker commands to make your container management smooth and efficient. Save this post for quick reference! 📌

🔹 Docker Basics:

# Check Docker version
docker --version

# Display Docker system information
docker info

# List all Docker commands
docker --help

🔹 Images:

# List all images
docker images

# Search for an image on Docker Hub
docker search <image-name>

# Pull an image from Docker Hub
docker pull <image-name>

# Build an image from a Dockerfile
docker build -t <image-name>:<tag> .

# Remove an image
docker rmi <image-id>

🔹 Containers:

# List all running containers
docker ps

# List all containers (including stopped ones)
docker ps -a

# Start a container
docker start <container-id>

# Stop a container
docker stop <container-id>

# Restart a container
docker restart <container-id>

# Remove a container
docker rm <container-id>

# Run a container
docker run -d --name <container-name> <image-name>

# Run a container with a specific port mapping
docker run -d -p <host-port>:<container-port> <image-name>

# Run a container with a volume
docker run -d -v <host-dir>:<container-dir> <image-name>

# Attach to a running container
docker attach <container-id>

🔹 Container Inspection & Logs:

# View logs of a container
docker logs <container-id>

# Follow logs of a container
docker logs -f <container-id>

# Inspect a container
docker inspect <container-id>

# View resource usage statistics of a container
docker stats <container-id>

🔹 Networks:

# List all networks
docker network ls

# Create a network
docker network create <network-name>

# Connect a container to a network
docker network connect <network-name> <container-id>

# Disconnect a container from a network
docker network disconnect <network-name> <container-id>

# Inspect a network
docker network inspect <network-name>

# Remove a network
docker network rm <network-name>

🔹 Volumes:

# List all volumes
docker volume ls

# Create a volume
docker volume create <volume-name>

# Inspect a volume
docker volume inspect <volume-name>

# Remove a volume
docker volume rm <volume-name>

🔹 Docker Compose:

# Start services defined in docker-compose.yml
docker-compose up

# Start services in detached mode
docker-compose up -d

# Stop services
docker-compose down

# View running services
docker-compose ps

# Build or rebuild services
docker-compose build

# View logs of services
docker-compose logs

🔹 Docker Cleanup:

# Remove all stopped containers
docker container prune

# Remove all unused images
docker image prune

# Remove all unused volumes
docker volume prune

# Remove all unused networks
docker network prune

Keep this list handy and make container management a breeze! Happy Dockering! 🎉


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

⚡️ If you want to become good at DevOps, then learn these use cases:


1️⃣) Kubernetes Cluster level logging architectures
✔️ https://lnkd.in/gFxEFm5A

2️⃣) How GitHub's Database Self-Destructed in 43 Seconds
✔️ https://lnkd.in/g3VPSEwj

3️⃣) Kubernetes Operator vs Helm - Which One to Choose ?
✔️ https://lnkd.in/gSeg56ME

4️⃣) Dockerfile vs. Docker Compose: What You Should Know
✔️ https://lnkd.in/g-q_TQzY

5️⃣) Multi Cloud GitOps Workflow for Kubernetes Management
✔️ https://lnkd.in/gUGNMk2T

6️⃣) How a Pod is Deleted - Behind the Scenes Breakdown
✔️ https://lnkd.in/geW8kaQm

7️⃣) How to Set up Disk and Bandwidth Limits in Docker
✔️ https://lnkd.in/gYHsfpmP



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

🚨 CI/CD ♾ real-time related Question & Answer:-


1. What is a CI/CD pipeline?
A CI/CD pipeline is an automated workflow that integrates and delivers code changes continuously. It consists of processes like code integration, building, testing, deployment, and delivery. The goal of CI/CD pipelines is to deliver software updates quickly, reliably, and consistently, reducing the risk of errors and improving collaboration.

2. How do you implement a CI/CD pipeline from scratch?
Version Control: Start by ensuring the code is managed in a version control system (e.g., Git).
Build Automation: Set up build automation tools (e.g., Jenkins, GitLab CI/CD, GitHub Actions) that will compile and package your code.
Testing: Integrate automated testing for unit, integration, and acceptance tests.
Artifact Repository: Use an artifact repository (e.g., Nexus, Artifactory) for storing build artifacts.
Deployment Automation: Automate the deployment process using tools like Ansible, Docker, or Kubernetes.
Monitoring and Alerts: Set up monitoring tools to alert about issues post-deployment.

3. What are the common stages of a CI/CD pipeline?
Source Code Control: Code commits trigger the pipeline.
Build: The code is compiled and packaged.
Test: Automated testing, including unit, integration, and functional tests, are run.
Release/Deploy: The code is deployed to staging or production environments.

4. How do you manage secrets in a CI/CD pipeline?
Using secret management tools (e.g., HashiCorp Vault, AWS Secrets Manager, Azure Key Vault).
Storing secrets in environment variables or vaults outside the codebase.
Using pipeline tools’ native secret management features (e.g., Jenkins credentials store).

5. Explain the importance of automated testing in CI/CD?
Automated testing ensures code quality by catching issues early in the pipeline, preventing faulty code from reaching production. It helps:
Maintain code consistency. Reduce human error. Accelerate feedback loops, allowing developers to fix issues faster.
Ensure that changes don’t introduce regressions.

6. How do you ensure that deployments are zero-downtime?
Use blue-green deployments or canary releases to gradually roll out new versions while keeping the old version live.
Leverage container orchestration platforms like Kubernetes, which can manage rolling updates. Ensure that the database schema and application logic are backward-compatible during updates.
Implement load balancers to route traffic between old and new versions.

8. How do you handle rollbacks in CI/CD?
Versioning Artifacts: Store previous builds and redeploy an older version in case of failure.
Blue-Green Deployments: Switch back to the old version if the new version fails.
Database Migrations: Use reversible migrations to ensure that changes can be rolled back easily.
Monitoring and Alerts: Integrate automated rollback triggers based on predefined metrics or errors.


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

🚀 DevOps Project 32: Real-Time CI/CD Pipeline for Java Application Deployment


☁️ Project Repository: DevOps Project 32 on GitHub

In today’s fast-paced software world, delivering high-quality software efficiently is a must. This project demonstrates how to set up a real-time CI/CD pipeline for a Java application, enabling seamless deployment to an Apache server.

✨ What You'll Learn:
✅ Automating builds and tests with tools like Jenkins & Maven
✅ Generating and deploying artifacts with Apache Maven
✅ Implementing version control integration & deployment automation
✅ Accelerating time-to-market while improving code quality

If you're looking to enhance your CI/CD skills and streamline your Java application deployments, this tutorial has you covered! 🚧

🛠 Dive in now and take your DevOps journey to the next level!

❤️‍🔥 Share with friends and learning aspirants ❤️‍🔥

📣 Note: Fork this Repository 🧑‍💻 for upcoming future projects, Every week releases new Project.

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

➡️Useful Terraform commands along with brief explanations:- ❤️

1. terraform init: Initializes a working directory containing Terraform configuration files.
2. terraform plan: Generates an execution plan, outlining actions Terraform will take.
3. terraform apply: Applies the changes described in the Terraform configuration.
4. terraform destroy: Destroys all resources described in the Terraform configuration.
5. terraform validate: Checks the syntax and validity of Terraform configuration files.
6. terraform refresh: Updates the state file against real resources in the provider.
7. terraform output: Displays the output values from the Terraform state.
8. terraform state list: Lists resources within the Terraform state.
9. terraform show: Displays a human-readable output of the current state or a specific resource's state.
10. terraform import: Imports existing infrastructure into Terraform state.
11. terraform fmt: Rewrites Terraform configuration files to a canonical format.
12. terraform graph: Generates a visual representation of the Terraform dependency graph.
13. terraform providers: Prints a tree of the providers used in the configuration.
14. terraform workspace list: Lists available workspaces.
15. terraform workspace select: Switches to another existing workspace.
16. terraform workspace new: Creates a new workspace.
17. terraform workspace delete: Deletes an existing workspace.
18. terraform output: Retrieves output values from a module.
19. terraform state mv: Moves an item in the state.
20. terraform state pull: Pulls the state from a remote backend.
21. terraform state push: Pushes the state to a remote backend.
22. terraform state rm: Removes items from the state.
23. terraform taint: Manually marks a resource for recreation.
24. terraform untaint: Removes the 'tainted' state from a resource.
25. terraform login: Saves credentials for Terraform Cloud.
26. terraform logout: Removes credentials for Terraform Cloud.
27. terraform force-unlock: Releases a locked state.
28. terraform import: Imports existing infrastructure into your Terraform state.
29. terraform plan -out: Saves the generated plan to a file.
30. terraform apply -auto-approve: Automatically applies changes without requiring approval.
31. terraform apply -target=resource: Applies changes only to a specific resource.
32. terraform destroy -target=resource: Destroys a specific resource.
33. terraform apply -var="key=value": Sets a variable's value directly in the command line.
34. terraform apply -var-file=filename.tfvars: Specifies a file containing variable definitions.
35. terraform apply -var-file=filename.auto.tfvars: Automatically loads variables from a file.


🎄 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

🚨 𝐍𝐚𝐮𝐤𝐫𝐢 𝐭𝐫𝐢𝐜𝐤𝐬 𝐰𝐡𝐢𝐜𝐡 𝐰𝐨𝐫𝐤𝐬 𝐢𝐧 𝟐𝟎𝟐𝟒

💎 𝐓𝐫𝐲 𝐭𝐡𝐞𝐬𝐞 𝐡𝐚𝐜𝐤𝐬 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐜𝐚𝐥𝐥𝐬

- Replace career gap by freelance in resume
- Create multiple naukri profile based on location
- Upadte job profile everyday in morning
- Add hot keywords related to job in resume
- Everyday apply for max job openings
- Check job desc to get those keywords
- For ex for DE: Pyspark, ADF, Databricks
- Find HR & send DM/ mails personally
- Make job profiles on multiple job portals
- Try all job searching platforms
- Like LinkedIn, referrals, Frnd N/w

Try some of these hacks and very sure you will get better calls than before.

▶️ PS : Easiest way to become lucky is to try more


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

In DevOps and CI/CD (Continuous Integration/Continuous Deployment) projects, different environments play crucial roles in the software development lifecycle. Let's explore the main types of deployment environments:

1️⃣. Development Environment:
- In the development environment, each programmer has an isolated workspace to write and tweak code without affecting others.
- Developers use this environment to build, test, and experiment with new features or changes.
- It's a stepping stone from local development to broader testing.
- Typically, it's less stable and more dynamic than other environments.

2️⃣. Staging Environment:
- The staging environment is where code goes before it gets shipped to production.
- It closely resembles the production environment but is separate from it.
- QA (Quality Assurance) teams and stakeholders thoroughly test the application here.
- Any issues discovered are addressed before moving to production.

3️⃣. Quality Assurance (QA) Environment:
- QA environments come in various forms, such as QA testing servers or dedicated QA clusters.
- QA teams perform comprehensive testing, including functional, performance, security, and regression testing.
- It's essential for identifying and fixing defects before deploying to production.

4️⃣. Production Environment:
- The production environment is the final destination for your code.
- It hosts the live application that end-users interact with.
- Stability, reliability, and performance are critical in this environment.
- Changes are carefully managed through CI/CD pipelines to minimize disruptions.


Remember that these environments serve specific purposes, and their configurations should align with the needs of your application and organization. Properly managing and maintaining these environments ensures a smooth software delivery process! 🚀

🌟 Sources:
1. The Ultimate CI/CD DevOps Pipeline Project
2. How to Manage Multiple Environments with DevOps
3. Deployment Environments: Everything You Need To Know As A DevOps Engineer
4. Tutorial: Deploy environments in CI/CD by using GitHub - Azure DevOps
5. Building Your First Azure DevOps CI/CD Pipeline: A Step-by-Step Guide [1] [2] [3] [4] [5]

➡️ Reference links: [1] [2] [3] [4] [5]



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