➡️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 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 𝗟𝗲𝘁'𝘀 𝗲𝘅𝗽𝗹𝗼𝗿𝗲 𝘁𝗵𝗲 𝗽𝗶𝗹𝗹𝗮𝗿𝘀 𝗼𝗳 𝗗𝗲𝘃𝗢𝗽𝘀 ♾ (𝘃𝗮𝗿𝗶𝗼𝘂𝘀 𝗗𝗲𝘃𝗢𝗽𝘀 𝘁𝗼𝗼𝗹𝘀)


🎄 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @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

📱 𝐆𝐢𝐭 𝐖𝐨𝐫𝐤𝐅𝐥𝐨𝐰


➡️ Getting Started
- 𝗜𝗻𝗶𝘁𝗶𝗮𝗹𝗶𝘇𝗲 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆: 𝚐𝚒𝚝 𝚒𝚗𝚒𝚝 🌱
- 𝗖𝗹𝗼𝗻𝗲 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆: 𝚐𝚒𝚝 𝚌𝚕𝚘𝚗𝚎 [𝚄𝚁𝙻] 📦

➡️ Working with Remotes
- 𝗟𝗶𝘀𝘁 𝗥𝗲𝗺𝗼𝘁𝗲𝘀: 𝚐𝚒𝚝 𝚛𝚎𝚖𝚘𝚝𝚎 -𝚟 📡
- 𝗔𝗱𝗱 𝗥𝗲𝗺𝗼𝘁𝗲: 𝚐𝚒𝚝 𝚛𝚎𝚖𝚘𝚝𝚎 𝚊𝚍𝚍 [𝚗𝚊𝚖𝚎] [𝚄𝚁𝙻] ➕📡
- 𝗥𝗲𝗺𝗼𝘃𝗲 𝗥𝗲𝗺𝗼𝘁𝗲: 𝚐𝚒𝚝 𝚛𝚎𝚖𝚘𝚝𝚎 𝚛𝚖 [𝚗𝚊𝚖𝚎] ➖📡
- 𝗙𝗲𝘁𝗰𝗵 𝗥𝗲𝗺𝗼𝘁𝗲 𝗖𝗵𝗮𝗻𝗴𝗲𝘀: 𝚐𝚒𝚝 𝚏𝚎𝚝𝚌𝚑 [𝚛𝚎𝚖𝚘𝚝𝚎] 🔄
- 𝗣𝘂𝗹𝗹 𝗖𝗵𝗮𝗻𝗴𝗲𝘀: 𝚐𝚒𝚝 𝚙𝚞𝚕𝚕 [𝚛𝚎𝚖𝚘𝚝𝚎] [𝚋𝚛𝚊𝚗𝚌𝚑] 🔽
- 𝗣𝘂𝘀𝗵 𝗖𝗵𝗮𝗻𝗴𝗲𝘀: 𝚐𝚒𝚝 𝚙𝚞𝚜𝚑 [𝚛𝚎𝚖𝚘𝚝𝚎] [𝚋𝚛𝚊𝚗𝚌𝚑] 🔼

➡️ Branching & Merging
- 𝗟𝗶𝘀𝘁 𝗕𝗿𝗮𝗻𝗰𝗵𝗲𝘀: 𝚐𝚒𝚝 𝚋𝚛𝚊𝚗𝚌𝚑 🌿
- 𝗖𝗿𝗲𝗮𝘁𝗲 𝗕𝗿𝗮𝗻𝗰𝗵: 𝚐𝚒𝚝 𝚋𝚛𝚊𝚗𝚌𝚑 [𝚗𝚊𝚖𝚎] ➕🌿
- 𝗦𝘄𝗶𝘁𝗰𝗵 𝗕𝗿𝗮𝗻𝗰𝗵: 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 [𝚗𝚊𝚖𝚎] ↔️ 🌿
- 𝗖𝗿𝗲𝗮𝘁𝗲 & 𝗦𝘄𝗶𝘁𝗰𝗵 𝗕𝗿𝗮𝗻𝗰𝗵: 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 -𝚋 [𝚗𝚊𝚖𝚎] ➕↔️ 🌿
- 𝗠𝗲𝗿𝗴𝗲 𝗕𝗿𝗮𝗻𝗰𝗵: 𝚐𝚒𝚝 𝚖𝚎𝚛𝚐𝚎 [𝚋𝚛𝚊𝚗𝚌𝚑] 🔄 🌿
- 𝗗𝗲𝗹𝗲𝘁𝗲 𝗕𝗿𝗮𝗻𝗰𝗵: 𝚐𝚒𝚝 𝚋𝚛𝚊𝚗𝚌𝚑 -𝚍 [𝚗𝚊𝚖𝚎] 😀 🌿

➡️ Making Changes
- 𝗦𝘁𝗮𝘁𝘂𝘀: 𝚐𝚒𝚝 𝚜𝚝𝚊𝚝𝚞𝚜 📊
- 𝗔𝗱𝗱 𝗖𝗵𝗮𝗻𝗴𝗲𝘀: 𝚐𝚒𝚝 𝚊𝚍𝚍 [𝚏𝚒𝚕𝚎/𝚍𝚒𝚛𝚎𝚌𝚝𝚘𝚛𝚢] ➕📄
- 𝗖𝗼𝗺𝗺𝗶𝘁 𝗖𝗵𝗮𝗻𝗴𝗲𝘀: 𝚐𝚒𝚝 𝚌𝚘𝚖𝚖𝚒𝚝 -𝚖 "[𝚖𝚎𝚜𝚜𝚊𝚐𝚎]" 👨‍💻
- 𝗔𝗺𝗲𝗻𝗱 𝗖𝗼𝗺𝗺𝗶𝘁: 𝚐𝚒𝚝 𝚌𝚘𝚖𝚖𝚒𝚝 --𝚊𝚖𝚎𝚗𝚍 👨‍💻
- 𝗥𝗲𝘀𝗲𝘁: 𝚐𝚒𝚝 𝚛𝚎𝚜𝚎𝚝 [𝚏𝚒𝚕𝚎] ⏪
- 𝗛𝗮𝗿𝗱 𝗥𝗲𝘀𝗲𝘁: 𝚐𝚒𝚝 𝚛𝚎𝚜𝚎𝚝 --𝚑𝚊𝚛𝚍 [𝚌𝚘𝚖𝚖𝚒𝚝] ⏪ 💥

➡️ Reviewing History
- 𝗟𝗼𝗴: 𝚐𝚒𝚝 𝚕𝚘𝚐 📜
- 𝗟𝗼𝗴 (𝗚𝗿𝗮𝗽𝗵): 𝚐𝚒𝚝 𝚕𝚘𝚐 --𝚐𝚛𝚊𝚙𝚑 📊 📜
- 𝗦𝗵𝗼𝘄 𝗖𝗵𝗮𝗻𝗴𝗲: 𝚐𝚒𝚝 𝚜𝚑𝚘𝚠 [𝚌𝚘𝚖𝚖𝚒𝚝] 🔍
- 𝗗𝗶𝗳𝗳: 𝚐𝚒𝚝 𝚍𝚒𝚏𝚏 [𝚋𝚛𝚊𝚗𝚌𝚑] 🆚

➡️ Cleanup & Maintenance
- 𝗦𝘁𝗮𝘀𝗵 𝗖𝗵𝗮𝗻𝗴𝗲𝘀: 𝚐𝚒𝚝 𝚜𝚝𝚊𝚜𝚑 📥
- 𝗔𝗽𝗽𝗹𝘆 𝗦𝘁𝗮𝘀𝗵: 𝚐𝚒𝚝 𝚜𝚝𝚊𝚜𝚑 𝚙𝚘𝚙 📤
- 𝗖𝗹𝗲𝗮𝗻 𝗨𝗻𝘁𝗿𝗮𝗰𝗸𝗲𝗱 𝗙𝗶𝗹𝗲𝘀: 𝚐𝚒𝚝 𝚌𝚕𝚎𝚊𝚗 -𝚏 🧽

➡️ Advanced & Miscellaneous
- 𝗥𝗲𝗯𝗮𝘀𝗲: 𝚐𝚒𝚝 𝚛𝚎𝚋𝚊𝚜𝚎 [𝚋𝚛𝚊𝚗𝚌𝚑] 🏗️
- 𝗖𝗵𝗲𝗿𝗿𝘆-𝗽𝗶𝗰𝗸: 𝚐𝚒𝚝 𝚌𝚑𝚎𝚛𝚛𝚢-𝚙𝚒𝚌𝚔 [𝚌𝚘𝚖𝚖𝚒𝚝] 🍒
- 𝗧𝗮𝗴: 𝚐𝚒𝚝 𝚝𝚊𝚐 [𝚗𝚊𝚖𝚎] 🏷️
- 𝗦𝗲𝗮𝗿𝗰𝗵 𝗟𝗼𝗴: 𝚐𝚒𝚝 𝚕𝚘𝚐 --𝚐𝚛𝚎𝚙="[𝚙𝚊𝚝𝚝𝚎𝚛𝚗]" 🔍 📜


🎄 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @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

🔔 DevOps, SRE, and Platform Engineering - making sense of the terminology! 🤔

Many enthusiasts whom I interviewed, didn't understand
the difference between DevOps, SRE, and Platform Engineering.

While these disciplines share similarities, there are nuances in their focus:

💻 DevOps emphasizes collaboration between dev and ops teams to optimize and accelerate software delivery.

📈 SRE focuses more on system reliability, availability, monitoring, and capacity planning.

🚀 Platform Engineering deals with building and managing the underlying infrastructure and platforms.

🔄 All three leverage automation, infra-as-code, and CI/CD.

📊 DevOps and SRE teams may own services end-to-end. Platform teams focus on shared platforms.

🎯 DevOps improves agility. SRE improves reliability. Platform Engineering improves developer productivity.

There's overlap in principles but differences in scope. Many organizations blend these roles for the best results.


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

AWS region vibes: 😎

The comparison: 😂


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

AWS ☁️ vs GCP ☁️ vs Azure ☁️ Cloud services Comparison Cheatsheet ⚡️


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

🚀 Explore More into CI/CD ♾ Tools on AWS Cloud ☁️

🖥 https://cloud.prodevopsguy.xyz/explore-more-into-cicd-tools-on-aws-cloud



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

📣 Job Opportunity: DevOps Engineers 📣

Looking for people having 6m to 1 Yr of experience in DevOps tools like Ansible, Docker, GitLab, Terraform and Python Scripting and Linux.

➡️ Job Location: Bengaluru

🔗 Please apply at ipxp.in/doeaf


✉️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @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

⚠️ 𝐖𝐡𝐲 𝟖𝟎% 𝐨𝐟 𝐂𝐥𝐨𝐮𝐝-𝐃𝐞𝐯𝐎𝐩𝐬 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐒𝐭𝐫𝐮𝐠𝐠𝐥𝐞 𝐰𝐢𝐭𝐡 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞
so let's go!!!

➡️𝐤𝐮𝐛𝐞-𝐚𝐩𝐢-𝐬𝐞𝐫𝐯𝐞𝐫: Handles API calls efficiently, scaling as needed. It's the gateway for interacting with Kubernetes, and processing commands and requests.

➡️𝐞𝐭𝐜𝐝: Stores important cluster data securely. Only the API server can directly access etcd, ensuring data integrity and consistency.

➡️𝐤𝐮𝐛𝐞-𝐬𝐜𝐡𝐞𝐝𝐮𝐥𝐞𝐫: Finds the best nodes for tasks based on resource availability and requirements. It's like a matchmaker, pairing workloads with suitable nodes.

➡️𝐜𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫-𝐦𝐚𝐧𝐚𝐠𝐞𝐫: Keeps things running smoothly by monitoring for changes and taking necessary actions. It handles tasks like cleaning up unused resources and managing namespaces.

➡️𝐂𝐥𝐨𝐮𝐝 𝐂𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫 𝐌𝐚𝐧𝐚𝐠𝐞𝐫: Connects your cluster to the cloud provider's features. It handles nodes, routes, and services, letting cloud features integrate smoothly with Kubernetes.

➡️𝐤𝐮𝐛𝐞𝐥𝐞𝐭: Ensures containers are healthy and manages node resources. It's like a caretaker, making sure containers are running well on their assigned nodes.

➡️𝐤𝐮𝐛𝐞-𝐩𝐫𝐨𝐱𝐲: Manages network configuration on nodes, facilitating communication between services and pods. It's like a traffic cop, directing network traffic within the cluster.

➡️𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫 𝐑𝐮𝐧𝐭𝐢𝐦𝐞: Manages containers and images, enabling them to work seamlessly on Kubernetes. It's the bridge between Kubernetes and container runtimes like Docker.

➡️𝐏𝐨𝐝𝐬: Bundles of processes that run until they finish their tasks. They're like temporary work crews, executing specific jobs within the cluster.


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

Let's talk about Kubernetes Gateway API.

It is a new way to manage traffic to Kubernetes services. 🤠

🔣How is it different from Ingress?
Ingress focuses on routing HTTP traffic.
While Gateway API supports a wider range of protocols, including HTTP, TCP, and gRPC.

🔣It also supports:

➡️HTTP Routing & TCP Routing
➡️HTTP Traffic Splitting (10% to service-1 and 90% to service-2)
➡️Cross-Namespace Routing
➡️Role-Based Access Control
➡️Enhanced Secuirty Controls


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

🌐 Here are 30 GitHub commands that are every DevOps Engineer to know.

1. 𝗴𝗶𝘁 𝗶𝗻𝗶𝘁: Initializes a new Git repository in the current directory.
2. 𝗴𝗶𝘁 𝗰𝗹𝗼𝗻𝗲 [𝘂𝗿𝗹]: Clones a repository into a new directory.
3. 𝗴𝗶𝘁 𝗮𝗱𝗱 [𝗳𝗶𝗹𝗲]: Adds a file or changes in a file to the staging area.
4. 𝗴𝗶𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 -𝗺 "[𝗺𝗲𝘀𝘀𝗮𝗴𝗲]": Records changes to the repository with a descriptive message.
5. 𝗴𝗶𝘁 𝗽𝘂𝘀𝗵: Uploads local repository content to a remote repository.
6. 𝗴𝗶𝘁 𝗽𝘂𝗹𝗹: Fetches changes from the remote repository and merges them into the local branch.
7. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘁𝘂𝘀: Displays the status of the working directory and staging area.
8. 𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵: Lists all local branches in the current repository.
9. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 [𝗯𝗿𝗮𝗻𝗰𝗵]: Switches to the specified branch.
10. 𝗴𝗶𝘁 𝗺𝗲𝗿𝗴𝗲 [𝗯𝗿𝗮𝗻𝗰𝗵]: Merges the specified branch's history into the current branch.
11. 𝗴𝗶𝘁 𝗿𝗲𝗺𝗼𝘁𝗲 -𝘃: Lists the remote repositories along with their URLs.
12. 𝗴𝗶𝘁 𝗹𝗼𝗴: Displays commit logs.
13. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁 [𝗳𝗶𝗹𝗲]: Unstages the file, but preserves its contents.
14. 𝗴𝗶𝘁 𝗿𝗺 [𝗳𝗶𝗹𝗲]: Deletes the file from the working directory and stages the deletion.
15. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘀𝗵: Temporarily shelves (or stashes) changes that haven't been committed.
16. 𝗴𝗶𝘁 𝘁𝗮𝗴 [𝘁𝗮𝗴𝗻𝗮𝗺𝗲]: Creates a lightweight tag pointing to the current commit.
17. 𝗴𝗶𝘁 𝗳𝗲𝘁𝗰𝗵 [𝗿𝗲𝗺𝗼𝘁𝗲]: Downloads objects and refs from another repository.
18. 𝗴𝗶𝘁 𝗺𝗲𝗿𝗴𝗲 --𝗮𝗯𝗼𝗿𝘁: Aborts the current conflict resolution process, and tries to reconstruct the pre-merge state.
19. 𝗴𝗶𝘁 𝗿𝗲𝗯𝗮𝘀𝗲 [𝗯𝗿𝗮𝗻𝗰𝗵]: Reapplies commits on top of another base tip, often used to integrate changes from one branch onto another cleanly.
20. 𝗴𝗶𝘁 𝗰𝗼𝗻𝗳𝗶𝗴 --𝗴𝗹𝗼𝗯𝗮𝗹 𝘂𝘀𝗲𝗿.𝗻𝗮𝗺𝗲 "[𝗻𝗮𝗺𝗲]" 𝗮𝗻𝗱 𝗴𝗶𝘁 𝗰𝗼𝗻𝗳𝗶𝗴 --𝗴𝗹𝗼𝗯𝗮𝗹 𝘂𝘀𝗲𝗿.𝗲𝗺𝗮𝗶𝗹 "[𝗲𝗺𝗮𝗶𝗹]": Sets the name and email to be used with your commits.
21. 𝗴𝗶𝘁 𝗱𝗶𝗳𝗳: Shows changes between commits, commit and working tree, etc.
22. 𝗴𝗶𝘁 𝗿𝗲𝗺𝗼𝘁𝗲 𝗮𝗱𝗱 [𝗻𝗮𝗺𝗲] [𝘂𝗿𝗹]: Adds a new remote repository.
23. 𝗴𝗶𝘁 𝗿𝗲𝗺𝗼𝘁𝗲 𝗿𝗲𝗺𝗼𝘃𝗲 [𝗻𝗮𝗺𝗲]: Removes a remote repository.
24. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 -𝗯 [𝗯𝗿𝗮𝗻𝗰𝗵]: Creates a new branch and switches to it.
25. 𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵 -𝗱 [𝗯𝗿𝗮𝗻𝗰𝗵]: Deletes the specified branch.
26. 𝗴𝗶𝘁 𝗽𝘂𝘀𝗵 --𝘁𝗮𝗴𝘀: Pushes all tags to the remote repository.
27. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗿𝗿𝘆-𝗽𝗶𝗰𝗸 [𝗰𝗼𝗺𝗺𝗶𝘁]: Picks a commit from another branch and applies it to the current branch.
28. 𝗴𝗶𝘁 𝗳𝗲𝘁𝗰𝗵 --𝗽𝗿𝘂𝗻𝗲: Prunes remote tracking branches no longer on the remote.
29. 𝗴𝗶𝘁 𝗰𝗹𝗲𝗮𝗻 -𝗱𝗳: Removes untracked files and directories from the working directory.
30. 𝗴𝗶𝘁 𝘀𝘂𝗯𝗺𝗼𝗱𝘂𝗹𝗲 𝘂𝗽𝗱𝗮𝘁𝗲 --𝗶𝗻𝗶𝘁 --𝗿𝗲𝗰𝘂𝗿𝘀𝗶𝘃𝗲: Initializes and updates submodules recursively.


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

🛡 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

𝗧𝗼𝗽 𝟱𝟬 🐧 𝗟𝗶𝗻𝘂𝘅 𝗖𝗼𝗺𝗺𝗮𝗻𝗱𝘀 𝘆𝗼𝘂 𝗺𝘂𝘀𝘁 𝗸𝗻𝗼𝘄 🚀

Some of the collection of Linux commands to be aware as a person in tech.


🔵 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs