🔥 DevOps Project-11: Deploy Two-Tier Architecture on AWS using Terraform ♾

🔗 Project Link: HERE
🔗 Detailed Blog Link: HERE

🔄 Project Overview :-
In the world of cloud computing, infrastructure as code (IaC) plays a pivotal role in automating the deployment and management of resources. This blog post provides a step-by-step guide on creating a Two-Tier architecture on AWS using Terraform. We’ll explore the essential services involved, ensuring high availability, security, and scalability for hosting a static website.

Also, we are adopting a modular approach with enhanced security measures. The infrastructure is organized into dedicated modules, ensuring a scalable, maintainable, and secure deployment.

❤️‍🔥 Share with friends and colleagues ❤️‍🔥

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


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

♾ DevOps and Cloud Engineering is not just about learning tools. ☄️

🔣 Learn basic working blocks for the long run:

1️⃣. How does networking work?
➡️ Keywords: TCP/IP, DNS, HTTP/S, VPN, Load Balancers, Firewalls, Network Protocols, Subnetting

2️⃣. How to pick the right database?
➡️ Keywords: SQL vs. NoSQL, ACID Properties, Scalability, Data Modeling

3️⃣. Principles of secure system design
➡️ Keywords: Encryption, Authentication, Authorization, OWASP Top 10, Security Policies, Risk Assessment, Compliance Standards (like GDPR, HIPAA).

4️⃣. What are the different kinds of storage?
➡️ Keywords: Block Storage, Object Storage, File Storage, NAS, SAN, Cloud Storage (AWS S3, Azure Blob), SSD vs. HDD.

5️⃣. What are different kinds of DR (Disaster Recovery) strategies?
➡️ Keywords: Backup and Restore, Pilot Light, Warm Standby, Multi-site, RTO (Recovery Time Objective), RPO (Recovery Point Objective).

6️⃣. Common approaches for data replication
➡️ Keywords: Master-Slave, Peer-to-Peer, Synchronous vs. Asynchronous, Data Consistency, Replication Topologies, Log Shipping.

7️⃣. When to implement caching mechanisms?
➡️ Keywords: In-memory Caches (Redis, Memcached), CDN, Cache Invalidation, Write-through vs. Write-back Cache, Cache Hit Ratio.

Tools and frameworks will change. Fundamentals remain intact.

Without fundamentals, you are incomplete.


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

What is Ansible →
➡️ Ansible is DevOps tool and it is similar like chef means it is a Configuration management tool let’s Begins with a Story → suppose you have a big organisation which have 100’s of servers Now a task is came to install git on that 100’s of servers …man responsible for doing this is System Administrator who is doing this manually which takes a lot of time…

guys!!!! we have that tool and that is Ansible→ A Configuration Management Tool…..
➡️ But !! But !! But !! First you need to connect all the nodes to ansible server which is done manually after that you will be able to automate the things…..
➡️ configuration management →It is a method through which we automate admin tasks.
➡️ It automates the task which the system administrator doing manually

Configuration management tool is of 2 types →
➡️ Pull based → In Pull Based it periodically check for the update from the main server to the nodes if update available it automatically install on the nodes connected with the server → chef and puppet is a pull based config tool.

➡️ Push based → In push based nodes is not going to the main server for the update the update is pushed to the nodes automatically for example the update of apps is pushed to your phone play store now it’s your choice whether you update or not → push based tool is Ansible when you need control in your hands so you take control of your own server for updating.

History of Ansible →
➡️ Michael Dehan developed Ansible in Feb 2012
➡️ Red Hat acquired the Ansible tool in 2015.
➡️ Ansible is available for RHEL, Debian, cent OS, Oracle Linux.
➡️ It is developed in Python background and also in Windows PowerShell.
➡️ You Can use this tool whether your server are in on premises or in the cloud.
➡️ It converted your code into infrastructure means you can say that it is a little bit called an Infrastructure building tool.


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

𝐋𝐢𝐬𝐭 𝐨𝐟 𝐟𝐫𝐞𝐞 𝐜𝐨𝐮𝐫𝐬𝐞𝐬 𝐭𝐨 𝐭𝐫𝐚𝐧𝐬𝐟𝐨𝐫𝐦 𝐘𝐨𝐮𝐫 𝐒𝐤𝐢𝐥𝐥𝐬: 𝐃𝐢𝐯𝐞 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐖𝐨𝐫𝐥𝐝 𝐨𝐟 𝐃𝐞𝐯𝐎𝐩𝐬 & 𝐁𝐚𝐜𝐤𝐞𝐧𝐝 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞𝐬𝐞 𝐦𝐮𝐬𝐭 𝐭𝐫𝐲 𝐅𝐫𝐞𝐞 𝐂𝐨𝐮𝐫𝐬𝐞𝐬

🔢. 𝐏𝐲𝐭𝐡𝐨𝐧:
A scripting language used for automation in DevOps.
🔗 https://lnkd.in/gTEsX2VC

🔢. 𝐆𝐢𝐭:
Distributes version control system handles everything from small to very large projects with speed and efficiency.
🔗 https://lnkd.in/gFTyTWCC

🔢. 𝐂𝐥𝐨𝐮𝐝:
Its fair to say the rapid increament of startUps is revolutionised by the cloud technology.
🔗 https://lnkd.in/gf6_8RNG

🔢. 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬:
An approach of making a loosely coupled application.
🔗 https://lnkd.in/gYqdHCdF

🔢. 𝐒𝐞𝐫𝐯𝐞𝐫𝐥𝐞𝐬𝐬:
Allows developers to build and run applications without worrying about servers.
🔗 https://lnkd.in/g8knM8uE

🔢. 𝐋𝐢𝐧𝐮𝐱:
Probably the most famous primitive yet secure OS to use
🔗 https://lnkd.in/ghmZybpz

🔢. 𝐃𝐞𝐯𝐎𝐩𝐬:
An exploding domain to learn (It is an ecosystem that takes care of continuous integration, delivery, deployment and monitoring)
🔗 https://lnkd.in/g6ryYv8N

🔢. 𝐃𝐨𝐜𝐤𝐞𝐫:
Packages application along with dependencies and libraries required to run the application.
🔗 https://lnkd.in/ggaqmu8p

🔢. 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬, 𝐎𝐩𝐞𝐧𝐒𝐡𝐢𝐟𝐭:
Manages the deployment of an application and have autoscaling and autohealing capabilities.
🔗 https://lnkd.in/gsKYTciW

🔢🔢. 𝐌𝐲𝐒𝐐𝐋:
Relational Database Management System
🔗 https://lnkd.in/gbmjQcsD


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

🟡 𝗬𝗼𝘂 𝗠𝗨𝗦𝗧 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 🐧𝗟𝗶𝗻𝘂𝘅 𝗳𝗶𝗹𝗲 𝘀𝘆𝘀𝘁𝗲𝗺

Linux's file system is tree-like. The base is "/", with everything else branching off.

➡️ Core Directories:

/bin 🛠: Essential binaries, e.g., bash, ls, grep.
/boot 🚀: Boot items like kernel & bootloader.
/dev 🔌: Device files for connected hardware.
/etc 📜: System configuration files.
/home 🏡: User home directories.
/lib 📚: Shared libraries for programs.
/media 💿: Mounts for removable media.
/mnt 🧲: Temporary mounts.
/opt 📦: Optional software.
/proc 📊: System, process, memory info.
/root 👑: Root user's home.
/sbin 🔧: System admin tools, e.g., init.
/srv 🌐: Data for services.
/tmp 🌡: Temporary files.
/usr 🖥: User software.
/var 🔄: Variable data, logs, temp files.

🐧 Linux Commands:

cd 🚶: Navigate.
ls 📋: List contents.
mkdir 📁: Create folder.
rmdir 🗑: Delete folder.
cp 📤: Copy.
mv 🚚: Move.
rm ❌: Delete.

⚠️ Note: Directories like /bin are crucial. Don't modify!

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

👾 CICD vs. CICD? You might be saying it wrong...

While CICD gets thrown around a lot, it actually refers to two separate practices that work together in the software development lifecycle: Continuous Integration (CI) and Continuous Delivery/Deployment (CD).

Here's a quick breakdown:

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 (𝗖𝗜): Automates the process of merging code changes from developers into a shared mainline frequently. This means every push triggers builds, tests, and catches bugs early on.

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆/𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 (𝗖𝗗): Takes CI a step further. It automates the entire delivery pipeline, allowing you to release new features or bug fixes to production environments quickly and reliably. CD can include manual approval gates before deployment, while Continuous Deployment (CD) automates deployments entirely.

Here's the key difference:

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆: Gives you a "deploy button" - the code is ready to be pushed to production with a manual go-ahead.

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁: Takes it a step further. If all automated tests pass in CD, the code is automatically deployed to production without human intervention.


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

💥 May the spirit of Holi bring you happiness. The warmth of Holi brings you joy, and the joy of Holi brings you hope. We wish you a joyous Holi! 💥

May this Holi be filled with fun, joy and love. Happy Holi 2024!


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

🌐 GitOps Workflow - Simplified Visual Guide

➡️ GitOps brought a shift in how software and infrastructure are managed with Git as the central hub for managing and automating the entire lifecycle of applications and infrastructure.

➡️ It's built on the principles of version control, collaboration, and continuous integration and deployment (CI/CD).


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

🔔 DevOps AWS (Freshers) Job opportunity

➡️Job Title: DevOps AWS (Freshers)
➡️Location: Hyderabad
➡️Company: RJAY technologies Pvt Ltd
➡️Job Type: Full-time

➡️Job Description:

We are seeking a highly motivated and enthusiastic individual to join our team as an AWS DevOps Engineer.

➡️ Required Skills:

AWS, Docker, kubernetes, Ansible,Linux,Shells Scripting, Python, Jenkins, CI/CD, Git/GitHub

✉️ To apply, please submit your resume to sreeja.k@rjaytechnologies.com


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

🔥 AWS DEVOPS REAL-TIME DEPLOYMENT

✨ Development → Pre-PROD → Production ⏰

🔗 Detailed Project Explanation with Screenshots : https://harshhaa.hashnode.dev/aws-devops-real-time-deployment-dev-pre-prod-production

🔗Project Source code: https://github.com/NotHarshhaa/AWS-DevOps_Real-Time_Deployment


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

☁️ 𝗔𝗪𝗦 𝗵𝗮𝘀 𝗼𝘃𝗲𝗿 𝟮𝟬𝟬 𝗳𝘂𝗹𝗹𝘆 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝗱 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀.✨
𝗠𝗼𝘀𝘁 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗔𝗪𝗦 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝘆𝗼𝘂 𝘀𝗵𝗼𝘂𝗹𝗱 𝗹𝗲𝗮𝗿𝗻 𝘁𝗼 𝗯𝗲 𝗮 𝗗𝗲𝘃𝗢𝗽𝘀 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿.

✔️Amazon EC2
✔️AWS IAM
✔️AWS CloudFormation
✔️AWS CloudWatch
✔️AWS CodePipeline
✔️AWS CodeBuild
✔️AWS CodeDeploy
✔️Amazon ECS
✔️AWS Lambda
✔️AWS Elastic Beanstalk
✔️Amazon DynamoDB


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

⚙️ 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬 𝐨𝐟 𝐌𝐨𝐝𝐞𝐫𝐧 𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐒𝐭𝐚𝐜𝐤

✅ 𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐚𝐬 𝐂𝐨𝐝𝐞 (𝐈𝐚𝐂) 𝐑𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐲
- Store all your Terraform code in a version-controlled repository.
- Enables collaboration and tracking changes over time.

✅ 𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧 𝐅𝐢𝐥𝐞𝐬
- Written in HashiCorp Configuration Language (HCL).
- Define the desired state of your infrastructure.

✅ 𝐒𝐭𝐚𝐭𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭
- Tracks the current state of your infrastructure.
- Stores information about resources managed by Terraform.

✅ 𝐏𝐫𝐨𝐯𝐢𝐝𝐞𝐫 𝐏𝐥𝐮𝐠𝐢𝐧𝐬
- Extend Terraform's capabilities to manage different cloud providers.
- Allow seamless integration with AWS, Azure, Google Cloud, etc.

✅ 𝐌𝐨𝐝𝐮𝐥𝐞𝐬
- Encapsulate reusable infrastructure components.
- Promote modularity and maintainability in Terraform code.

✅ 𝐑𝐞𝐦𝐨𝐭𝐞 𝐁𝐚𝐜𝐤𝐞𝐧𝐝
- Store Terraform state remotely for better collaboration.
- Provides locking mechanisms to prevent concurrent modifications.

✅ 𝐂𝐈 / 𝐂𝐃 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞
- Automate the process of building, testing, and deploying infrastructure changes.
- Ensures consistency and reliability in infrastructure deployments.

✅ 𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐓𝐞𝐬𝐭𝐢𝐧𝐠 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤
- Validate infrastructure changes before applying them.
- Helps prevent misconfigurations and downtime.

✅ 𝐒𝐞𝐜𝐫𝐞𝐭 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭
- Securely manage sensitive information like API keys and passwords.
- Integrates with tools like HashiCorp Vault or AWS Secrets Manager.

✅ 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 𝐚𝐧𝐝 𝐋𝐨𝐠𝐠𝐢𝐧𝐠 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧
- Monitor the health and performance of your infrastructure.
- Capture and analyze logs to troubleshoot issues efficiently.

✅ 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐚𝐧𝐝 𝐆𝐨𝐯𝐞𝐫𝐧𝐚𝐧𝐜𝐞 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧
- Enforce compliance policies and regulatory requirements.
- Automate governance tasks to maintain security and compliance standards.

✅ 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧 𝐓𝐨𝐨𝐥𝐬
- Facilitate communication and knowledge sharing among team members.
- Document infrastructure changes, decisions, and best practices.


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @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

To ace your 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬 for a DevOps Engineer role ,following Linux related Hardware commands, Data information, Process mgmt., files mgmt, search patterns and packages commands you should be aware of:

𝟏: 𝐇𝐀𝐑𝐃𝐖𝐀𝐑𝐄 𝐈𝐍𝐅𝐎𝐑𝐌𝐀𝐓𝐈𝐎𝐍:
-cat /proc/cpuinfo # Display CPU information
-cat /proc/meminfo # Display memory information
-free -h # Display free and used memory ( -hfor human readable, -mfor MB, -gfor GB.)
-lspci -tv # Display PCI devices
-lsusb -tv # Display USB devices
-dmidecode # Display DMI/SMBIOS (hardware info) from the BIOS
-hdparm -i /dev/sda # Show info about disk sda
-hdparm -tT /dev/sda # Perform a read speed test on disk sda

𝟐. 𝐌𝐀𝐍𝐈𝐏𝐔𝐋𝐀𝐓𝐈𝐍𝐆 𝐃𝐀𝐓𝐀 :
-awk # Pattern scanning and processing language
-perl # Data manipulation language
-cmp # Compare the contents of two files
-paste # Merge file data
-sed # Stream text editor
-cut # Cut out selected fields of each line of a file
-sort # Sort file data
-diff # Differential file comparator
-split # Split file into smaller files
-expand, unexpand # Expand tabs to spaces, and vice versa

𝟑. 𝐏𝐑𝐎𝐂𝐄𝐒𝐒 𝐌𝐀𝐍𝐀𝐆𝐄𝐌𝐄𝐍𝐓:
ps # Display your currently running processes
ps -ef # Display all the currently running processes on the system.
ps -ef | grep processname # Display process information for processname
top # Display and manage the top processes
htop # Interactive process viewer (top alternative)
kill pid # Kill process with process ID of pid
killall processname # Kill all processes named processname
program & # Start programin the background
bg # Display stopped or background jobs
fg # Brings the most recent background job to foreground
fg n # Brings job nto the foreground


𝟒. 𝐀𝐑𝐂𝐇𝐈𝐕𝐄𝐒 (𝐓𝐀𝐑 𝐅𝐈𝐋𝐄𝐒) :
-tar cf archive.tar directory # Create tar named archive .tar containing dir.
-tar xf archive.tar # Extract the contents from archive.tar. tar czf
-archive.tar.gz director # Create a gzip compressed tar file name archive.tar
-tar xzf archive.tar.gz # Extract a gzip compressed tar file.
-tar cjf archive.tar.bz2 directory # Create a tar file with bzip2 compression
-tar xjf archive.tar.bz2 # Extract a bzip2 compressed tar file.

𝟓. 𝐈𝐍𝐒𝐓𝐀𝐋𝐋𝐈𝐍𝐆 𝐏𝐀𝐂𝐊𝐀𝐆𝐄𝐒:
yum search keyword # Search for a package by keyword.
yum install package # Install package.
yum info package # Display desc and summary information about package.
rpm -i package.rpm # Install package from local file named package.rpm
yum remove package # Remove/uninstall package
tar zxvf sourcecode.tar.gz # Install software from source code.

𝟔. 𝐒𝐄𝐀𝐑𝐂𝐇 :
grep pattern file # Search for pattern in file
grep -r pattern directory # Search recursively for patternin directory
locate name # Find files and directories by name
find /home/john -name 'prefix*' # Find files in /home/john that start with "prefix".
find /home -size +100M # Find files larger than 100MB in /home


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

👍 Multi-Stage Build Images used in CICD ♾

➡️ Every microservice should be its own separate container. If you only use a single-stage Docker build, you’re probably missing out on some powerful features of the build process. On the other hand, a multi-stage Docker build has many advantages over a single-stage build for deploying microservices.

➡️ Some Advantages are :
- Optimizes the overall size of the Docker image
- Removes the burden of creating multiple Dockerfiles for different stages
- Easy to debug a particular build stage
- Able to use the previous stage as a new stage in the new environment
- Ability to use the cached image to make the overall process quicker
- Reduces the risk of vulnerabilities found as the image size becomes smaller with multi-stage builds


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

In Kubernetes, readiness and liveness probes are mechanisms used to ensure that applications running inside containers are healthy and able to handle traffic properly. They are essential for maintaining the reliability and availability of applications in a Kubernetes cluster.

📢 Readiness Probe:
🎤 The readiness probe is used to determine when a container is ready to start accepting traffic. It is crucial for ensuring that services don't send requests to a container until it's ready to handle them effectively.

🎤If the readiness probe fails (returns a non-successful HTTP status code or times out), Kubernetes marks the container as not ready, and it won't receive any traffic until the probe succeeds.

🎤The readiness probe can be configured to use HTTP endpoints, TCP sockets, or custom scripts to determine the readiness of the container.

📢 Liveness Probe:
🎤The liveness probe is used to check if a container is still running properly. It helps Kubernetes determine whether a container should be restarted if it's unresponsive or in a failed state.

🎤Unlike the readiness probe, which determines if the container is ready to serve traffic, the liveness probe checks if the container is still functioning correctly after it has started.

🎤If the liveness probe fails (returns a non-successful HTTP status code or times out), Kubernetes restarts the container to try to recover it.

⚠️ Both the readiness and liveness probes are configured to perform an HTTP GET request to the /healthz endpoint on port 8080 of the container.

➡️The readiness probe will start 5 seconds after the container starts and will be performed every 10 seconds thereafter.

➡️The liveness probe will start 10 seconds after the container starts and will be performed every 15 seconds thereafter.

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

🔥 Understanding Kubernetes Logs - A Comprehensive Guide

🔣 Kubernetes logs are your essential toolkit for spotting and solving container app issues

➡️ Without that valuable insight, you'd be navigating in the dark, risking prolonged downtime and frustrated users.


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

📣 If you're in IT, learning Python 🐍 can open endless possibilities!

It's a versatile skill that can take you far, and it's known for being one of the easiest programming languages to learn and understand.

Here's a roadmap to help you master Python:

🔢. 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗕𝗮𝘀𝗶𝗰𝘀: This includes data types, control flow, functions, and object-oriented programming.

🔢. 𝗘𝘅𝗽𝗹𝗼𝗿𝗲 𝗣𝘆𝘁𝗵𝗼𝗻 𝗟𝗶𝗯𝗿𝗮𝗿𝗶𝗲𝘀: Python boasts a vast ecosystem of libraries for everything from web development to data science to machine learning. Once you're comfortable with the fundamentals, delve into popular libraries like NumPy, pandas, Matplotlib, and scikit-learn.

🔢. 𝗕𝘂𝗶𝗹𝗱 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀: The best way to solidify your Python knowledge is by doing. Start building projects that pique your interest, like a web application, a data analysis dashboard, or a machine learning model.

🔢. 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁: Once you have some projects under your belt, learn how to deploy them for others to use. Python applications can be deployed in various ways, using web servers or container orchestration platforms.

🔢. 𝗧𝗲𝘀𝘁 𝗬𝗼𝘂𝗿 𝗖𝗼𝗱𝗲: Regularly testing your code ensures it functions as expected. Python offers various testing frameworks, including unittest and pytest.

🔢. 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗣𝗼𝗿𝘁𝗳𝗼𝗹𝗶𝗼: Showcase your Python development skills by building a portfolio of your work. This will be a valuable asset when demonstrating your capabilities to potential employers.

🔢. 𝗨𝗽𝗱𝗮𝘁𝗲 𝗬𝗼𝘂𝗿 𝗥𝗲𝘀𝘂𝗺𝗲: Highlight your experience with Python libraries, projects, and deployments by revamping your resume.


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

➡️ Understanding Container Runtimes in Kubernetes 👈

A container runtime in Kubernetes is the software component responsible for managing the lifecycle of individual containers within a pod. It's the engine that executes the commands and manages the processes within the container environment.

➡️ What it does:

➡️Creates and starts containers: Based on instructions from the kubelet (the Kubernetes agent on each node), the container runtime pulls the container image, sets up the necessary resources, and fires up the container process.

➡️Manages container resources: It allocates CPU, memory, and other resources as specified in the pod definition, ensuring each container gets its fair share.

➡️Monitors and manages container health: It keeps an eye on the container's health and restarts it if it crashes or becomes unresponsive.

➡️Stops and removes containers: When a container is no longer needed, the runtime gracefully stops it and cleans up its resources.

➡️ Why it's important:

➡️Isolation: Container runtimes create isolated environments for each container, ensuring applications don't interfere with each other or the host system.

➡️Security: They enforce security policies and resource limitations, providing a more secure environment for containerized applications.

➡️Portability: Container runtimes adhere to industry standards, allowing containers to be easily moved between different platforms and cloud providers.

➡️Common container runtimes in Kubernetes.

- containerd
- CRI-O
- Docker Engine
- Mirantis Container Runtime


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