📣 Docker 🐬 basics for beginners


🖥 Let's learn how we can develop, deploy and run applications easily with Docker!

➡️If you Google Docker, you will find that Docker is a software platform that uses an OS-level virtualization to create self-contained containers.
➡️You may have created multiple Virtual Machines with Oracle VM or Vagrant before. Docker is something like that (but better, but more about that later).
➡️With Docker, we select an image (think about Docker images as recipes) and download it. Then, we create an instance of that image or container, pretty similar to a Virtual Machine.

𝑓𝑜𝑟 𝑚𝑜𝑟𝑒 𝑖𝑛𝑓𝑜, 𝑦𝑜𝑢 𝑐𝑎𝑛 𝑐ℎ𝑒𝑐𝑘 𝑡ℎ𝑖𝑠 𝑙𝑖𝑛𝑘:
🖱https://prodevopsguy.site/docker-basics-for-beginners


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

DevOps ♾ Real-time Day to Day activities that every DevOps Engineer should Know


➡️The daily activities of a DevOps engineer can vary depending on the specific organization, project, and team structure. However, here are some common tasks and responsibilities that DevOps engineers typically engage in on a day-to-day basis:

𝑓𝑜𝑟 𝑚𝑜𝑟𝑒 𝑖𝑛𝑓𝑜, 𝑦𝑜𝑢 𝑐𝑎𝑛 𝑐ℎ𝑒𝑐𝑘 𝑡ℎ𝑖𝑠 𝑙𝑖𝑛𝑘:
🖥 https://prodevopsguy.site/devops-day-to-day-activities-by-devops-engineer


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

🚨 Deploying an app on Azure involves a few steps. Let's walk through them:


1. Create and Set Up Your Azure Account:
Sign in to your Azure portal.
If you're new to Azure, follow the Microsoft-Azure portal guide to get started.

2. Build Your Web Application:
Create your web app using your preferred tech stack (e.g., C#, Java, Python, etc.).
You can host your code on GitHub or any other Version Control System.

3. Create a Resource Group:
Resource groups help manage access control and resource allocation.
If you don't have an existing resource group, create a new one in the Azure portal.

4. Set Up Your Web App Service:
In the Azure portal, navigate to "App Services."
Choose the "Create" option and customize settings:

Basics: Select the resource group, name your web app, choose a region, and set the runtime stack (e.g., Java, .NET, etc.).
Deployment: Configure continuous deployment from GitHub or other sources.
Other tabs allow further customization (networking, monitoring, tags).
Review and create your web app.

5. Deploy Your Web App:
Click on your web app's name in App Services.
Find the "Default domain" link, which is the deployed URL.
Access your web app and modify it as needed.

Remember, there are various approaches and options for deploying web apps on Azure. Choose the one that best suits your requirements and application complexity[1]. Happy deploying! 🚀🔵

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


📱 𝗙𝗼𝗹𝗹𝗼𝘄 @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

➡️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 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

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

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

𝗗𝗼𝗰𝗸𝗲𝗿 🐬 𝗖𝗼𝘀𝘁 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 :-

✅ 𝐎𝐩𝐭𝐢𝐦𝐢𝐳𝐞 𝐲𝐨𝐮𝐫 𝐃𝐨𝐜𝐤𝐞𝐫 𝐛𝐮𝐢𝐥𝐝𝐬 𝐢𝐬 𝐛𝐲 𝐮𝐬𝐢𝐧𝐠 𝐚 .𝐝𝐨𝐜𝐤𝐞𝐫𝐢𝐠𝐧𝐨𝐫𝐞 𝐟𝐢𝐥𝐞 to exclude unnecessary files and directories from the build context, similar to a .gitignore file. This reduces the amount of data sent to the Docker daemon during builds, speeding up the build process and reducing resource consumption.

✅ 𝐕𝐞𝐫𝐬𝐢𝐨𝐧 𝐏𝐢𝐧𝐧𝐢𝐧𝐠 𝐟𝐨𝐫 𝐃𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐢𝐞𝐬: To ensure consistency and prevent unexpected changes during builds, it’s advisable to pin versions of the packages and base images you are using. This practice not only helps in making builds more predictable but also optimizes the use of the build cache by avoiding unnecessary invalidations when dependencies are updated.

✅ 𝐌𝐢𝐧𝐢𝐦𝐢𝐳𝐢𝐧𝐠 𝐭𝐡𝐞 𝐢𝐦𝐚𝐠𝐞 𝐬𝐢𝐳𝐞 𝐛𝐲 𝐜𝐥𝐞𝐚𝐧𝐢𝐧𝐠 𝐮𝐩 𝐮𝐧𝐧𝐞𝐜𝐞𝐬𝐬𝐚𝐫𝐲 𝐟𝐢𝐥𝐞𝐬 𝐚𝐧𝐝 𝐝𝐢𝐫𝐞𝐜𝐭𝐨𝐫𝐢𝐞𝐬 within your Dockerfile can also lead to cost savings in storage and transfer. This includes removing temporary files and caches that are not needed in the final image.

✅ 𝐔𝐬𝐢𝐧𝐠 𝐥𝐢𝐠𝐡𝐭𝐰𝐞𝐢𝐠𝐡𝐭 𝐛𝐚𝐬𝐞 𝐢𝐦𝐚𝐠𝐞𝐬 is a highly effective strategy for optimizing Docker costs. Alpine Linux is a popular choice due to its minimal footprint, which can significantly reduce the overall size of your containers. This reduction in size not only decreases storage costs but also speeds up the time required for downloading and deploying images, making your operations more efficient.

✅ 𝐑𝐞𝐠𝐮𝐥𝐚𝐫𝐥𝐲 𝐩𝐫𝐮𝐧𝐢𝐧𝐠 𝐮𝐧𝐮𝐬𝐞𝐝 𝐃𝐨𝐜𝐤𝐞𝐫 𝐨𝐛𝐣𝐞𝐜𝐭𝐬 𝐬𝐮𝐜𝐡 𝐚𝐬 𝐢𝐦𝐚𝐠𝐞𝐬, 𝐜𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬, 𝐯𝐨𝐥𝐮𝐦𝐞𝐬, 𝐚𝐧𝐝 𝐧𝐞𝐭𝐰𝐨𝐫𝐤𝐬 is an essential practice to free up disk space and enhance the performance of your Docker environment

✅ 𝐌𝐚𝐧𝐚𝐠𝐢𝐧𝐠 𝐭𝐡𝐞 𝐯𝐨𝐥𝐮𝐦𝐞 𝐨𝐟 𝐥𝐨𝐠𝐬 𝐠𝐞𝐧𝐞𝐫𝐚𝐭𝐞𝐝 𝐛𝐲 𝐃𝐨𝐜𝐤𝐞𝐫 𝐜𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 is crucial for preventing excessive disk usage and associated costs. Docker offers several strategies for configuring log rotation and retention policies.

✅ 𝐎𝐩𝐭𝐢𝐦𝐢𝐳𝐢𝐧𝐠 𝐡𝐞𝐚𝐥𝐭𝐡 𝐜𝐡𝐞𝐜𝐤𝐬 𝐟𝐨𝐫 𝐃𝐨𝐜𝐤𝐞𝐫 𝐜𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 is essential for ensuring that your applications run smoothly without wasting resources on unnecessary operations. Properly configured health checks help prevent the deployment of unhealthy containers that can degrade performance and increase costs due to resource wastage.

✅ 𝐒𝐞𝐭𝐭𝐢𝐧𝐠 𝐫𝐞𝐬𝐨𝐮𝐫𝐜𝐞 𝐥𝐢𝐦𝐢𝐭𝐬 𝐨𝐧 𝐃𝐨𝐜𝐤𝐞𝐫 𝐜𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 is crucial to ensure efficient resource use and prevent any single service from consuming more than its fair share.


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

🔔 Looking for resources to learn Terraform. Here are some free courses, tutorials and YouTube links! 👇

➡️YouTube resources:
1️⃣. Terraform Zero to Hero: https://lnkd.in/gvAm6xRF

2️⃣. Terraform in Basics: https://lnkd.in/g2yEnbbc

3️⃣. Terraform Best Practices: https://lnkd.in/gJaQ2Mr4

4️⃣. Terraform Basics: https://lnkd.in/gJaQ2Mr4

➡️Terraform courses:
1️⃣. Basics of Terraform: https://lnkd.in/g5dbxbwA

2️⃣. Terraform 101: https://lnkd.in/giKJm3_C

3️⃣. Terraform + AWS: https://lnkd.in/gJt6rzWx

4️⃣. Terraform on Azure : https://lnkd.in/g8SvbMTv

5️⃣. Basics of Terraform: https://lnkd.in/g9BxxAZ4

6️⃣. Terraform for beginners: https://lnkd.in/gPzANE99

➡️Terraform concepts and tutorials:
1⃣. Terraform beginners: https://lnkd.in/gpi6kNDe

2⃣. Introduction to terraform: https://lnkd.in/gAwwzG4N

3⃣. Terraform Tutorial: https://lnkd.in/gmxCKSZV


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

📢 DevOps Project-24: Real-Time DevSecOps Pipeline with Jenkins for a Dot Net Web App


🔗 Project Link: HERE

📶 Project Overview :-
We will be deploying a .NET-based application. This is an everyday use case scenario used by several organizations. We will be using Jenkins as a CICD tool and deploying our application on a Docker Container and Kubernetes cluster.

This project shows the detailed metric i.e. CPU Performance of our instance where this project is launched.


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

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

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

Tech News ‼️

➡️ Microsoft to lay off hundreds at Azure cloud unit.

➡️ Google lays off 100 Employees in its Cloud unit.

➡️ Instagram testing feature that stops users from skipping ads.

➡️ Truecaller AI Call Scanner can help you to prevent Voice call scams.

➡️ London hospitals cyber attack causing significant impact on services.

➡️ Intel launches new Xeon server processors amid competition with AMD.

Want more Tech News Like this? Join our WhatsApp group
https://chat.whatsapp.com/FndTPrJEkbq5RlKQE3jGp3

⚡️ Deploying a Kubernetes Cluster on Azure Kubernetes Service(AKS) with Terraform ⚡️


♾ https://www.prodevopsguy.tech/posts/deploying-a-kubernetes-cluster-on-azure-kubernetes-serviceaks-with-terraform

🤝🤝🤝🤝

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

DevOps professionals can benefit from various certifications to enhance their skills and marketability. Here are some valuable DevOps certifications:


1️⃣. Certified Kubernetes Administrator (CKA): This certification focuses on Kubernetes, the popular container orchestration tool. It covers installation, configuration, networking, and security aspects of Kubernetes. The CKA credential demonstrates your expertise in managing Kubernetes clusters[1].

2️⃣. AWS Certified DevOps Engineer - Professional: Offered by Amazon Web Services (AWS), this certification validates your ability to design, deploy, and manage AWS applications and infrastructure using DevOps practices. It's highly regarded by employers[2].

3️⃣. Docker Certified Associate (DCA): Docker is widely used for containerization. The DCA certification assesses your knowledge of Docker concepts, container management, and orchestration. It's valuable for DevOps engineers working with containers[2].

4️⃣. Puppet Certified Professional: If you're involved in configuration management, consider this certification. It focuses on Puppet, a popular tool for automating infrastructure management[2].

5️⃣. Microsoft Certified: DevOps Engineer Expert: For those working in Microsoft Azure environments, this certification demonstrates your expertise in implementing DevOps practices using Azure tools and services[2].

Remember to choose certifications based on your career goals and the technologies you work with. Each certification provides a unique skill set that can boost your DevOps career! 🚀🔧

⚡️Reference links: [1] [2] [3] [4]


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

As a DevOps engineer, mastering Linux commands is crucial for efficient system administration and management. Here are some essential commands you'll find useful:


1️⃣. File and Disk Management:
ls: Lists files and directories in the current directory.
ls -l: Lists files and directories with detailed information (permissions, ownership, size, modification date).
ls -a: Lists all files and directories, including hidden ones.
cat: Displays file contents (options include -b, -n, -s, and -E).
chmod: Changes file or directory permissions.
chown: Changes ownership of a file or directory.
tail: Displays the last 10 lines of a specified file.
dd: Copies raw data from one file/device to another.
find: Searches for files and directories based on specific criteria[1].


⚡️. User and Permission Management:
useradd: Adds a new user.
passwd: Sets or changes a user's password.
chpasswd: Changes passwords in batch mode.
usermod: Modifies user properties.
userdel: Deletes a user.
sudo: Executes commands with superuser privileges.
su: Switches to another user account.
chgrp: Changes group ownership of files or directories[2].


⚡️. Process and Service Management:
ps: Lists running processes.
top: Displays real-time system resource usage.
kill: Terminates a process.
systemctl: Manages system services (start, stop, enable, disable).
journalctl: Views system logs.
cron: Schedules tasks to run at specified intervals.
service: Controls system services (legacy command)[3].


⚡️. Networking and System Monitoring:
ifconfig or ip: Displays network interface information.
netstat: Shows network statistics.
ping: Tests network connectivity.
traceroute: Traces the route to a destination.
ss: Displays socket statistics.
df: Shows disk space usage.
du: Estimates file and directory space usage.
free: Displays memory usage.
uptime: Shows system uptime[4].


Remember to explore and practice these commands to become proficient in Linux for your DevOps workflows! 🚀🐧

💎 Reference links: [1] [2] [3] [4]


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

🚀 Terraform Commands for DevOps Engineers 🌍

Mastering Terraform can greatly enhance your infrastructure management. Here’s a quick reference to essential Terraform commands:


1️⃣ terraform init - Initialize a Terraform working directory.

2️⃣ terraform validate - Check the configuration for syntax errors.

3️⃣ terraform plan - Generate and show an execution plan.

4️⃣ terraform apply - Apply the changes required to reach the desired state.

5️⃣ terraform destroy - Destroy the Terraform-managed infrastructure.

6️⃣ terraform show - Show the current state or a saved plan.

7️⃣ terraform output - Extract the value of an output variable from the state file.

8️⃣ terraform state - Advanced state management commands:
- terraform state list - List resources in the state.
- terraform state show - Show a resource in the state.
- terraform state rm - Remove a resource from the state.

9️⃣ terraform fmt - Reformat configuration files to the canonical format.

1️⃣0️⃣ terraform taint - Manually mark a resource for recreation.

1️⃣1️⃣ terraform untaint - Manually unmark a resource as tainted.

1️⃣2️⃣ terraform import - Import existing infrastructure into your Terraform state.

1️⃣3️⃣ terraform refresh - Update the state file with the real infrastructure.

📘 Helpful Links:
- Terraform Documentation: https://www.terraform.io/docs/index.html
- Terraform Best Practices: https://www.terraform-best-practices.com

Keep this cheat sheet handy and automate your infrastructure with confidence! 💡

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

🔴 𝐎𝐛𝐬𝐞𝐫𝐯𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐰𝐢𝐭𝐡 𝐆𝐫𝐚𝐟𝐚𝐧𝐚, 𝐋𝐨𝐤𝐢, 𝐚𝐧𝐝 𝐭𝐡𝐞 𝐆𝐫𝐚𝐟𝐚𝐧𝐚 𝐀𝐠𝐞𝐧𝐭

Visualizing logs, metrics, and traces has never been easier!

This diagram illustrates the seamless integration between Grafana, Loki, and the Grafana Agent, enabling you to collect, visualize, and analyze all your observability data in one place.

➡️ 𝐇𝐞𝐫𝐞'𝐬 𝐡𝐨𝐰 𝐢𝐭 𝐰𝐨𝐫𝐤𝐬:

✅ 𝐆𝐫𝐚𝐟𝐚𝐧𝐚 𝐀𝐠𝐞𝐧𝐭: Collects logs from various sources, including your firewall, filesystem, applications, and Kubernetes clusters. It also scrapes Prometheus metrics and discovers Prometheus targets and rules.

✅ 𝐆𝐫𝐚𝐟𝐚𝐧𝐚 𝐋𝐨𝐤𝐢: Centralizes log storage and management, allowing you to query and analyze your logs efficiently.

✅ 𝐆𝐫𝐚𝐟𝐚𝐧𝐚: Provides a powerful and user-friendly interface for visualizing all your logs, metrics, and traces. You can create dashboards and alerts to monitor your system health and performance in real-time.

𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬 𝐨𝐟 𝐮𝐬𝐢𝐧𝐠 𝐆𝐫𝐚𝐟𝐚𝐧𝐚, 𝐋𝐨𝐤𝐢, 𝐚𝐧𝐝 𝐭𝐡𝐞 𝐆𝐫𝐚𝐟𝐚𝐧𝐚 𝐀𝐠𝐞𝐧𝐭 𝐭𝐨𝐠𝐞𝐭𝐡𝐞𝐫:

✅ 𝐈𝐦𝐩𝐫𝐨𝐯𝐞𝐝 𝐨𝐛𝐬𝐞𝐫𝐯𝐚𝐛𝐢𝐥𝐢𝐭𝐲: Gain a deeper understanding of your system's health and performance by visualizing all your data in one place.

✅ 𝐅𝐚𝐬𝐭𝐞𝐫 𝐭𝐫𝐨𝐮𝐛𝐥𝐞𝐬𝐡𝐨𝐨𝐭𝐢𝐧𝐠: Quickly identify and diagnose issues with the help of centralized logs and real-time monitoring.

✅ 𝐒𝐢𝐦𝐩𝐥𝐢𝐟𝐢𝐞𝐝 𝐝𝐚𝐭𝐚 𝐦𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Streamline your data collection and analysis workflows with a unified platform.


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

📌 https://blog.prodevopsguy.xyz/100-kubernetes-diagnostics-commands-with-kubectl

🔗 More DevOps Blogs : HERE

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

Follow 🍩 Like 👍 Share 👍 Comment Your thoughts 💬

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

⚡️ https://blog.prodevopsguy.xyz/100-linux-best-practices-by-prodevopsguy-tech


⚡️ More DevOps Blogs : HERE

🤝🤝🤝🤝

Follow 🍩 Like 👍 Share 👍 Comment Your thoughts 💬

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

🚀 𝐁𝐮𝐢𝐥𝐝 𝐑𝐨𝐛𝐮𝐬𝐭 𝐂𝐈/𝐂𝐃 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞𝐬! ✨

Continuous Integration and Continuous Deployment (CI/CD) are essential for maintaining agility and efficiency. By automating the integration, testing, and deployment processes, CI/CD pipelines minimize manual errors and accelerate the release cycle.

🔍 𝐖𝐡𝐲 𝐢𝐬 𝐂𝐈/𝐂𝐃 𝐜𝐫𝐮𝐜𝐢𝐚𝐥?

✅ 𝐒𝐩𝐞𝐞𝐝 𝐚𝐧𝐝 𝐄𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐜𝐲: Rapid, reliable deployments to meet business needs swiftly.

✅ 𝐐𝐮𝐚𝐥𝐢𝐭𝐲 𝐚𝐧𝐝 𝐑𝐞𝐥𝐢𝐚𝐛𝐢𝐥𝐢𝐭𝐲: Automated testing ensures high-quality releases.

✅ 𝐑𝐞𝐝𝐮𝐜𝐞𝐝 𝐑𝐢𝐬𝐤: Smaller, more manageable changes reduce the risk of major errors.

⭐ 𝑬𝒏𝒉𝒂𝒏𝒄𝒆 𝒀𝒐𝒖𝒓 𝑪𝑰/𝑪𝑫 𝒘𝒊𝒕𝒉 𝑨𝒕𝒎𝒐𝒔𝒍𝒚

➡️Atmosly streamlines your CI/CD processes, integrating effortlessly into your existing workflow to provide advanced analytics and real-time feedback. With Atmosly, deployments are not just faster—they're smarter.

➡️ Discover how Atmosly can transform your CI/CD pipeline into a cornerstone of your development strategy.


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

13 𝐦𝐨𝐬𝐭 𝐜𝐨𝐦𝐦𝐨𝐧𝐥𝐲 𝐮𝐬𝐞𝐝 𝐜𝐨𝐦𝐦𝐚𝐧𝐝 𝐟𝐨𝐫 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 🎯

Here are 13 of the most commonly used kubectl commands for managing a real production Kubernetes environment, along with explanations and common use cases:

✅ 𝐂𝐨𝐫𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭

#1 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐠𝐞𝐭
→ kubectl get pods (list pods)
→ kubectl get deployments (list deployments)
→ kubectl get services (list services)
→ kubectl get all (list most resources in a namespace)

#2 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐝𝐞𝐬𝐜𝐫𝐢𝐛𝐞
→ kubectl describe pod my-pod
→ kubectl describe node my-node

#3 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐜𝐫𝐞𝐚𝐭𝐞
→ kubectl create -f my-deployment.yaml

#4 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐚𝐩𝐩𝐥𝐲
→ kubectl apply -f my-deployment.yaml (apply a deployment definition)

#5 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐝𝐞𝐥𝐞𝐭𝐞
→ kubectl delete pod my-pod
→ kubectl delete service my-service

✅ Debugging and Troubleshooting

#6 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐥𝐨𝐠𝐬
→ kubectl logs my-pod
→ kubectl logs my-pod -c my-container (specify a container)

#7 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐞𝐱𝐞𝐜
→ kubectl exec -it my-pod -- bash (interactive shell)

#8 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐩𝐨𝐫𝐭-𝐟𝐨𝐫𝐰𝐚𝐫𝐝
→ kubectl port-forward my-pod 8080:80

#9 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐭𝐨𝐩
→ kubectl top pod (pod resource usage)
→ kubectl top node (node resource usage)

#10 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐞𝐱𝐩𝐥𝐚𝐢𝐧
→ kubectl explain pod
→ kubectl explain pod.spec (more specific)

✅ Managing Workloads

#11 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐫𝐨𝐥𝐥𝐨𝐮𝐭
→ kubectl rollout status deployment/my-deployment
→ kubectl rollout undo deployment/my-deployment

#12 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐬𝐜𝐚𝐥𝐞
→ kubectl scale deployment/my-deployment --replicas=5

#13 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐞𝐝𝐢𝐭
→ kubectl edit deployment my-deployment


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