🛠 Essential Azure CLI Commands for DevOps Engineers 🛠


📌 Setup and Configuration:

# Install Azure CLI
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

# Login to Azure
az login

# Set default subscription
az account set --subscription <subscription-id>

📌 Resource Groups:

# List resource groups
az group list

# Create resource group
az group create --name <resource-group-name> --location <location>

# Delete resource group
az group delete --name <resource-group-name> --yes --no-wait

📌 VM Management:

# List VMs
az vm list

# Create VM
az vm create --resource-group <resource-group-name> --name <vm-name> --image <image> --admin-username <username> --admin-password <password>

# Start VM
az vm start --resource-group <resource-group-name> --name <vm-name>

# Stop VM
az vm stop --resource-group <resource-group-name> --name <vm-name>

📌 Storage Accounts:

# List storage accounts
az storage account list

# Create storage account
az storage account create --name <account-name> --resource-group <resource-group-name> --location <location> --sku <sku>

# Delete storage account
az storage account delete --name <account-name> --resource-group <resource-group-name>

📌 Azure Kubernetes Service (AKS):

# List AKS clusters
az aks list

# Create AKS cluster
az aks create --resource-group <resource-group-name> --name <cluster-name> --node-count <node-count> --enable-addons monitoring --generate-ssh-keys

# Get AKS credentials
az aks get-credentials --resource-group <resource-group-name> --name <cluster-name>

📌 App Services:

# List App Services
az webapp list

# Create App Service
az webapp create --resource-group <resource-group-name> --plan <app-service-plan> --name <app-name> --runtime <runtime>

# Delete App Service
az webapp delete --resource-group <resource-group-name> --name <app-name>

📌 Azure DevOps:

# List Azure DevOps organizations
az devops organization list

# Create Azure DevOps project
az devops project create --name <project-name> --organization <organization-url>

# List Azure DevOps pipelines
az pipelines list --organization <organization-url> --project <project-name>

# Run Azure DevOps pipeline
az pipelines run --name <pipeline-name> --organization <organization-url> --project <project-name>

📌 Azure Monitor:

# List monitor activity logs
az monitor activity-log list

# Create alert rule
az monitor metrics alert create --name <alert-name> --resource-group <resource-group-name> --scopes <resource-id> --condition "<condition>" --action <action-group-id>

🔗 For more detailed commands and options, refer to the Azure CLI Command Reference


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

⛈ Knowing these 20 AWS ☁️ services makes you an AWS DevOps expert!

⏩Infra as code
- AWS CloudFormation
- AWS CDK

⏩Monitoring & Logging
- AWS CloudWatch
- AWS CloudTrail

⏩CI/CD
- AWS CodePipeline
- AWS CodeBuild
- AWS CodeDeploy

⏩Configuration Management
- AWS Systems Manager
- AWS OpsWorks

⏩Security
- AWS IAM
- AWS KMS

⏩Networking
- AWS VPC
- AWS Direct Connect

⏩Containers
- AWS ECS
- AWS ECR
- AWS EKS

⏩Serverless
- AWS Lambdas
- AWS API Gateway

⏩Databases
- AWS RDS
- AWS DynamoDB


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

🎉 Big Thanks from the ProDevOpsGuy Tech Community! 🎉

We’ve hit a milestone of 10,000 members! 🚀

We are incredibly grateful for each one of you who has joined our journey towards mastering DevOps and Cloud technologies.

⏩ On this channel, you’ll continue to get:

📈 Daily Trending DevOps/Cloud Blogs
📜 All Cloud Related Code & Scripts
💼 DevOps/Cloud Job Posts
🗂 Real-time Interview Questions & Preparation Guides

Your support and engagement make all the difference. Here’s to many more milestones together! 🌟

Stay tuned for more top-notch content and let’s keep growing! 💪


Join our Official Social Networks :
📱 Telegram // 📱 WhatsApp // 📱 GitHub // 📱 Instagram // 📱 Website


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

DevOps ♾ Integration Flow 💡

It refers to the set of practices, tools, and pipelines that improve the collaboration between software development and IT operations.

The goal is to shorten the system development life cycle and provide continuous delivery of high-quality software.

Here are the elements of the integration flows in a DevOps environment:

> Source Code Management
> Continuous Integration
> Configuration Management
> Containerization
> Continuous Deployment/Delivery
> Monitoring & Logging
> Feedback Loop

Elements in the image:

✅ Code Commit - Once the developers finish their code, they commit these changes to GitHub

✅ GitHub - GitHub is a Git repository hosting service, that allows developers to store code changes centrally

✅ CICD - When a change is made in GitHub, this process triggers Jenkins

✅ Jenkins - This is a tool used for automated continuous integration and continuous delivery

✅ Jenkins File - This file specifies what kind of operations Jenkins will carry out

✅ Build - Jenkins compiles (or "builds") the code that developers uploaded

✅ Maven - This is a build tool used for Java projects, handling dependency management

✅ Build Docker Image - A runnable Docker image of the application is created

✅ Push to Docker Hub - The Docker image that was created is pushed to an image repository service like Docker Hub

✅ Docker - Docker is a platform used for running applications in containers

This workflow represents a common structure found in modern software development practices and provides a good model for CI and CD.

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

Docker 🐬 🆚 Kubernetes ☸️

While Docker simplifies the containerization process, managing a fleet of containers at scale requires a robust orchestration platform like Kubernetes. Kubernetes automates container deployment, scaling, and management, allowing you to focus on building your applications without worrying about infrastructure complexities.

Docker and Kubernetes are complementary technologies that together form a powerful ecosystem for building, deploying, and managing modern applications. Whether you’re a developer looking to streamline your development workflow with Docker or an operations engineer seeking to orchestrate containerized workloads at scale with Kubernetes, embracing these technologies can propel your organization towards greater agility, scalability, and innovation in the ever-evolving world of software development.


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

📢 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗖𝗿𝗮𝘀𝗵𝗟𝗼𝗼𝗽𝗕𝗮𝗰𝗸𝗢𝗳𝗳 𝗲𝗿𝗿𝗼𝗿 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗶𝘁 & 𝗵𝗼𝘄 𝘁𝗼 𝗳𝗶𝘅 𝗶𝘁?

🔣𝐂𝐫𝐚𝐬𝐡𝐋𝐨𝐨𝐩𝐁𝐚𝐜𝐤𝐨𝐟𝐟 is an error state that occurs when a Pod fails to start, K8s tries to restart it, it fails again and this cycle continues. This usually means that a deeper problem is consistently causing your Pod to crash upon startup.

You can easily detect if your Pod is experiencing this error. Run “𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐠𝐞𝐭 𝐩𝐨𝐝𝐬”. The faulty Pod’s status is “𝐂𝐫𝐚𝐬𝐡𝐋𝐨𝐨𝐩𝐁𝐚𝐜𝐤𝐨𝐟𝐟 ”.

🔣𝗛𝗼𝘄 𝗱𝗼 𝗜 𝗳𝗶𝘅 𝘁𝗵𝗶𝘀?

1️⃣ 𝐂𝐡𝐞𝐜𝐤 𝐭𝐡𝐞 𝐥𝐨𝐠𝐬
Use “𝑘𝑢𝑏𝑒𝑐𝑡𝑙 𝑙𝑜𝑔𝑠 <𝑝𝑜𝑑-𝑛𝑎𝑚𝑒>” to know what’s actually going on inside your pod’s container(s). Most likely this will reveal why your app is unable to start.

⚡️ 𝐄𝐧𝐬𝐮𝐫𝐞 𝐬𝐮𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐭 𝐫𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬
Insufficient CPU/Memory can cause pods to crash. Set appropriate resource limits and deploy on Nodes that can actually provide a sufficient amount.

⚡️ 𝐂𝐡𝐞𝐜𝐤 𝐟𝐨𝐫 𝐈𝐦𝐚𝐠𝐞 𝐢𝐬𝐬𝐮𝐞𝐬
Often, the container image you specified does not exist or is in a private repository and your authentication is misconfigured. K8s can never pull the image to run in such cases.

⚡️ 𝐂𝐡𝐞𝐜𝐤 𝐟𝐨𝐫 𝐚𝐩𝐩 𝐜𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧 𝐢𝐬𝐬𝐮𝐞𝐬
Check the environment variables, config files and secrets supplied to your application. Depending on the environment (prod, dev, etc), you should be supplying the right set.

5️⃣ 𝐂𝐡𝐞𝐜𝐤 𝐟𝐨𝐫 𝐕𝐨𝐥𝐮𝐦𝐞 𝐦𝐨𝐮𝐧𝐭 𝐢𝐬𝐬𝐮𝐞𝐬
Pods can crash if they don’t get the persistent volumes they require.


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

🐬 Docker Workflow

It all starts with a developer. They write and test the application's code and define the necessary dependencies and libraries that the application needs to run.

1⃣ Dockerfile: A text document that tells 🐬 how to build and run your application. It defines the environment, dependencies, and runtime parameters using commands like FROM, RUN, COPY, etc.

🔢 Docker Image: Built from the Dockerfile, it's a static snapshot of the application and its environment. This image allows the application to run on any 🐬 platform.

🔢 Docker Container: When Docker Images are run, they create isolated instances known as containers. Each container runs the application in the same way, regardless of the environment.

🔢 Docker Hub: A cloud service to store, share, and manage Docker images. Developers upload their own images, download others', and collaborate on shared images.

This workflow:

➡️ Developer writes the application code
➡️ Dockerfile is prepared with build instructions
➡️ Docker Image is created, encapsulating the application and its dependencies
➡️ Image is used to run Docker Containers for testing or shared on Docker Hub
➡️ Others pull and run the image on their own systems or in production

This process streamlines development and deployment across different environments. 📱

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

Let's walk through essential 🐧 Linux commands -

📂 𝟭. 𝗙𝗶𝗹𝗲 𝗮𝗻𝗱 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝘆 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 🗂
- 𝚕𝚜: List files and directories in the current location
- 𝚙𝚠𝚍: Display the current working directory path
- 𝚌𝚍: Navigate between directories
- 𝚖𝚔𝚍𝚒𝚛: Create new directories
- 𝚛𝚖𝚍𝚒𝚛: Remove empty directories
- 𝚝𝚘𝚞𝚌𝚑: Create new files
- 𝚌𝚙: Duplicate files or directories
- 𝚖𝚟: Move or rename files and directories
- 𝚛𝚖: Delete files or directories

🔧 𝟮. 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁
- 𝚙𝚜: View running processes
- 𝚝𝚘𝚙: Monitor active processes in real-time
- 𝚑𝚝𝚘𝚙: Interact with processes using a user-friendly interface
- 𝚔𝚒𝚕𝚕: Stop a specific process
- 𝚔𝚒𝚕𝚕𝚊𝚕𝚕: Terminate all occurrences of a process
- 𝚙𝚜𝚝𝚛𝚎𝚎: Visualize processes in a hierarchical tree structure 🌲

👥 𝟯. 𝗨𝘀𝗲𝗿 𝗮𝗻𝗱 𝗚𝗿𝗼𝘂𝗽 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁
- 𝚙𝚊𝚜𝚜𝚠𝚍: Update user passwords
- 𝚞𝚜𝚎𝚛𝚊𝚍𝚍: Create new users
- 𝚞𝚜𝚎𝚛𝚍𝚎𝚕: Remove users
- 𝚐𝚛𝚘𝚞𝚙𝚜: List groups a user belongs to
- 𝚞𝚜𝚎𝚛𝚖𝚘𝚍: Modify user account details
- 𝚒𝚍: Show user and group information
- 𝚐𝚛𝚘𝚞𝚙𝚊𝚍𝚍: Create new groups
- 𝚐𝚛𝚘𝚞𝚙𝚍𝚎𝚕: Remove groups

💾 𝟰. 𝗦𝘆𝘀𝘁𝗲𝗺 𝗜𝗻𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 🖥
- 𝚞𝚗𝚊𝚖𝚎: Display system details
- 𝚍𝚏: Check disk space usage
- 𝚍𝚞: Estimate file and directory sizes
- 𝚏𝚛𝚎𝚎: Show available memory
- 𝚕𝚜𝚌𝚙𝚞: Provide CPU architecture information
- 𝚕𝚜𝚑𝚠: List hardware components
- 𝚕𝚜𝚋𝚕𝚔: Display block devices

🌐 𝟱. 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 🕸
- 𝚒𝚏𝚌𝚘𝚗𝚏𝚒𝚐: Manage network interfaces
- 𝚒𝚙: Control routing, devices, and tunnels
- 𝚙𝚒𝚗𝚐: Verify network connectivity
- 𝚗𝚎𝚝𝚜𝚝𝚊𝚝: Analyze network statistics
- 𝚜𝚜: Investigate socket connections
- 𝚝𝚛𝚊𝚌𝚎𝚛𝚘𝚞𝚝𝚎: Track packet routes and delays
- 𝚜𝚜𝚑: Establish secure remote connections
- 𝚗𝚌: Swiss army knife for TCP/IP networking

📦 𝟲. 𝗣𝗮𝗰𝗸𝗮𝗴𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 📥
- 𝚊𝚙𝚝-𝚐𝚎𝚝, 𝚊𝚙𝚝: Manage packages on Debian-based systems
- 𝚢𝚞𝚖, 𝚍𝚗𝚏: Handle packages on RPM-based systems
- 𝚛𝚙𝚖: Manage RPM packages
- 𝚍𝚙𝚔𝚐: Manage Debian packages
- 𝚜𝚗𝚊𝚙: Work with the universal Linux package system
- 𝚣𝚢𝚙𝚙𝚎𝚛: Manage packages on openSUSE

📜 𝟳. 𝗙𝗶𝗹𝗲 𝗩𝗶𝗲𝘄𝗶𝗻𝗴 𝗮𝗻𝗱 𝗘𝗱𝗶𝘁𝗶𝗻𝗴 📝
- 𝚌𝚊𝚝: Display file contents
- 𝚕𝚎𝚜𝚜: View files with navigation controls
- 𝚖𝚘𝚛𝚎: Another file viewing tool
- 𝚟𝚒𝚖: Use the powerful Vim text editor
- 𝚐𝚎𝚍𝚒𝚝: Edit files using the GNOME text editor
- 𝚗𝚊𝚗𝚘: Edit files with the user-friendly Nano editor


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

🚀 DevOps Project: Deploy a 3 Tier Architecture On AWS - End to End Project


Project Overview:
⚡️ Tier 1: Presentation Layer
✅ Create a web application using a framework like React, Angular, or Vue.js.
✅ Host the frontend on Amazon S3 or use AWS Amplify for a serverless frontend deployment.

⚡️ Tier 2: Application Layer
✅ Develop a server-side application using a technology like Node.js, Python, or Java.
✅ Deploy the application on AWS Elastic Beanstalk or AWS Lambda for serverless applications.
✅ Use Amazon API Gateway for creating RESTful APIs or AWS App Runner for containerized applications.

⚡️ Tier 3: Data Layer
✅ Choose a database solution like Amazon RDS (Relational Database Service), Amazon DynamoDB (NoSQL), or Amazon Aurora (MySQL/PostgreSQL).
✅ Configure database security groups and access controls.
✅ Ensure data backup and redundancy as per your application's needs.

Check for full details 👇

📱 Link: https://github.com/NotHarshhaa/DevOps-Projects/tree/master/DevOps-Project-01


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

🔔 Azure DevOps Complete Zero to Hero Guide 2024


Azure DevOps is a suite of services you can implement end-to-end DevOps in your organization. It includes services such as Azure Repos, Boards, Wiki, Build and Release pipelines, Test plans, Artifacts, etc.,

➡️ This Azure DevOps guide includes the following services:
🔖 Azure Boards: A project management tool that assists teams in planning, tracking, and discussing work.
🔖 Azure Pipelines: A continuous integration/continuous delivery (CI/CD) platform that automates software development, testing, and deployment.
🔖 Azure Repos: A Git repository hosting service that offers code version control.
🔖 Azure Artifacts: A centralized storage and management system for software artifacts such as NuGet packages and Docker images.
🔖 Azure Test Plans: A test management solution that assists teams in planning, executing, and analyzing tests.

𝑓𝑜𝑟 𝑚𝑜𝑟𝑒 𝑖𝑛𝑓𝑜, 𝑦𝑜𝑢 𝑐𝑎𝑛 𝑐ℎ𝑒𝑐𝑘 𝑡ℎ𝑖𝑠 𝑙𝑖𝑛𝑘:
🖥 https://prodevopsguy.site/azure-devops-hero-to-zero-guide


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

🚨 𝗧𝘆𝗽𝗲𝘀 𝗼𝗳 𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝘀 𝗶𝗻 𝗗𝗼𝗰𝗸𝗲𝗿 🐬


➡️𝑩𝒓𝒊𝒅𝒈𝒆:-
The default networking driver in Docker. This allows containers on the same host to talk to each other. If container A and B are on the same Bridge network, they can talk to each-other.

But if they’re on different bridge networks, they cannot talk to each other.
When you create a new network, unless you specify a different driver, it will be a Bridge network. Docker already creates one bridge network for you when you install it. And when you run a new container on your system, by default it connects to this bridge network.

➡️𝑯𝒐𝒔𝒕 :-
The host network driver can be used to remove network isolation between the container and its host machine. Unlike in bridge, a host network Container doesn’t get its own IP address. When it binds to a port, it is directly the host port. Host mode is useful for better performance because there’s no additional network layer in between. But it only works on Linux unless you use Docker Desktop.

➡️𝑶𝒗𝒆𝒓𝒍𝒂𝒚 :-
Overlay networks allow Docker containers on different host machines to talk to each other. They connect the Docker daemons running on these hosts to each other. This allows you to scale out horizontally. You don’t have to deploy all your containers on the same server.

➡️𝑵𝒐𝒏𝒆 :-
This means your container does not have any network and it is completely isolated from the host as well as other containers. This is more secure than the other drivers since all network communication is disabled. But of course, it is only good for some use cases.


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

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

📢 DevOps Project - 26: Automate Infrastructure on AWS Using Terraform and GitLab CICD


🔗 Project Link: HERE


📝 Project Structure:
⏩ Manual Setup:
- Write Terraform code to define and provision infrastructure.
- Manually create and configure infrastructure resources using the written code.

⏩ Automation:
- Develop a CI/CD pipeline on GitLab to automate the infrastructure provisioning and deployment processes.
- Integrate Terraform with the GitLab pipeline to ensure consistent and repeatable infrastructure setup.


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

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

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

𝗖𝗜/𝗖𝗗 ♾ 𝗕𝗲𝘀𝘁 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀

➡️𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 & 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗦𝗵𝗮𝗿𝗶𝗻𝗴
- Document everything about how the CI/CD pipelines work and share it with the team.
- Create guides (like runbooks) to help troubleshoot and fix problems quickly.

➡️𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 & 𝗟𝗼𝗴𝗴𝗶𝗻𝗴
- Keep an eye on the pipelines in real-time and gather logs to understand what's happening.
- Set up alerts to notify the team if something goes wrong.

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁
- Make sure the different environments (like development and production) are the same.
- Use rolling deployments to update software smoothly, and feature toggles to control new features.

➡️𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝗖𝗼𝗻𝘁𝗿𝗼𝗹
- Organize code changes well using branches, and have rules for how to add code.
- Review code changes to catch mistakes and keep things tidy.

➡️𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗠𝗲𝗮𝘀𝘂𝗿𝗲𝘀
- Check the code for security issues automatically.
- Test for problems with other software your project depends on.

➡️𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗕𝘂𝗶𝗹𝗱𝘀
- Use tools to build the software automatically and keep things consistent.
- Manage the pieces of code created during the build process carefully.

➡️𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗧𝗲𝘀𝘁𝗶𝗻𝗴
- Run tests automatically to make sure everything works.
- Do this often, and run tests at the same time to save time.

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻
- Keep adding code changes and testing them often.
- Make sure the build process happens automatically, and let the team know when it's done.

💳 Post Credit -: TheAlpha.Dev


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

CICD 👾 with Jenkins Multibranch pipeline ⚙️


➡️What is Jenkins Multibranch pipeline ❓
According to official documentation, multibranch pipeline job type lets you define a job where from a single git repository Jenkins will detect multiple branches and create nested jobs when it finds a Jenkinsfile

𝑓𝑜𝑟 𝑚𝑜𝑟𝑒 𝑖𝑛𝑓𝑜, 𝑦𝑜𝑢 𝑐𝑎𝑛 𝑐ℎ𝑒𝑐𝑘 𝑡ℎ𝑖𝑠 𝑙𝑖𝑛𝑘:
🖥 https://prodevopsguy.site/cicd-jenkins-multibranch-pipeline


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

💡 Know your responsibilities.

If you take out the tools, there are generic role specific requirements that companies will expect from you once you are onboard.

Keeping it simple, there are 4 levels for a DevOps role in IT.

➡️ DevOps Associate/Engineer: Level 1
- Collaborate with developers and IT staff to manage code releases.
- Assist in automating processes to improve efficiency.
- Implement and maintain CI/CD pipelines.
- Monitor system performance and troubleshoot issues.
- Assist in the design and implementation of infrastructure as code (IaC).

➡️ DevOps Engineer: Level 2
- Manage and improve CI/CD pipelines.
- Automate operational processes.
- Implement and manage monitoring and logging solutions.
- Collaborate with development and operations teams to ensure smooth deployment and operation of systems.
- Troubleshoot and resolve issues in development, test, and production environments.
- Implement and manage containerization and orchestration technologies (e.g., Docker, Kubernetes).

➡️ Senior DevOps Engineer: Level 3
- Lead and mentor junior members of the DevOps team.
- Architect and design highly available and scalable systems.
- Evaluate new technologies and tools to improve the DevOps process.
- Develop and implement best practices for infrastructure automation and configuration management.
- Collaborate with other teams to improve overall system reliability and performance.

➡️ Principal DevOps Engineer: Level 4
- Define the overall DevOps strategy for the organization.
- Lead large-scale infrastructure and automation projects.
- Drive innovation and continuous improvement within the DevOps team.
- Act as a subject matter expert for DevOps practices and technologies.
- Collaborate with executive leadership to align DevOps initiatives with business goals.


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

🚀 Ansible Commands Every DevOps Engineer Should Know 🚀


Ansible is a powerful tool for automation and configuration management. Here's a handy list of essential Ansible commands that will boost your productivity:

1. Check Ansible Version

   ansible --version
   

2. Ping All Hosts

   ansible all -m ping
   

3. Run a Command on All Hosts

   ansible all -a "uptime"
   

4. Use a Specific Inventory File

   ansible all -i /path/to/inventory -m ping
   

5. Run a Playbook

   ansible-playbook playbook.yml
   

6. Check Syntax of a Playbook

   ansible-playbook playbook.yml --syntax-check
   

7. List Hosts in Inventory

   ansible-inventory --list -i /path/to/inventory
   

8. Test a Playbook with Dry Run

   ansible-playbook playbook.yml --check
   

9. Encrypt a File with Ansible Vault

   ansible-vault encrypt filename.yml
   

10. Decrypt a File with Ansible Vault

    ansible-vault decrypt filename.yml
    

11. View Encrypted File with Ansible Vault

    ansible-vault view filename.yml
    

12. Edit an Encrypted File with Ansible Vault

    ansible-vault edit filename.yml
    

13. Create a New Vault Password File

    ansible-vault create vault-password-file
    

14. Run a Playbook with a Vault Password File

    ansible-playbook playbook.yml --vault-password-file /path/to/vault-password-file
    

15. Gather Facts About Hosts

    ansible all -m setup
    

16. Display All Modules

    ansible-doc -l
    

17. Get Documentation for a Specific Module

    ansible-doc <module_name>
    

18. Check the Status of a Service

    ansible all -m service -a "name=httpd state=started"
    

19. Copy a File to Hosts

    ansible all -m copy -a "src=/path/to/source dest=/path/to/destination"
    

20. Run a Task as a Different User

    ansible all -m command -a "ls -alh /home/user" -u username
    

Stay efficient and keep automating! 🛠✨


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