⚙️ 100 Kubernetes Commands With Examples


🦠 The Kubernetes command-line tool, kubectl—though extremely helpful—is flavored with numerous commands with several options. Searching for the right command or syntax can be like finding a needle in a haystack.

⛔ That’s why, we have compiled 100 essential kubectl commands with code examples in this article to help you streamline your Kubernetes management tasks.

𝑓𝑜𝑟 𝑚𝑜𝑟𝑒 𝑖𝑛𝑓𝑜, 𝑦𝑜𝑢 𝑐𝑎𝑛 𝑐ℎ𝑒𝑐𝑘 𝑡ℎ𝑖𝑠 𝑙𝑖𝑛𝑘:
❤️‍🔥 https://prodevopsguy.site/kubernetes-commands-with-examples


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

Top 100 ♾ DevOps Interview Questions and Answers (Beginners to Advanced)

🖥 https://blog.prodevopsguy.xyz/top-100-devops-interview-questions-and-answers


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

🚀 Essential OpenShift Commands for DevOps Engineers 🚀


🔧 Managing Projects and Namespaces

- Create a new project:

  oc new-project <project-name>
  

- Switch to a project:

  oc project <project-name>
  

- Delete a project:

  oc delete project <project-name>
  

🔧 Working with Pods

- List all pods:

  oc get pods
  

- Describe a specific pod:

  oc describe pod <pod-name>
  

- Delete a pod:

  oc delete pod <pod-name>
  

🔧 Deployments and Builds

- Deploy a new application:

  oc new-app <image-name>
  

- View deployment status:

  oc status
  

- Start a new build:

  oc start-build <build-config-name>
  

🔧 Services and Routes

- List all services:

  oc get services
  

- Create a new route:

  oc expose svc/<service-name>
  

- Get route details:

  oc get route <route-name>
  

🔧 ConfigMaps and Secrets

- Create a ConfigMap:

  oc create configmap <configmap-name> --from-literal=<key>=<value>
  

- Create a Secret:

  oc create secret generic <secret-name> --from-literal=<key>=<value>
  

- List all ConfigMaps and Secrets:

  oc get configmaps
  oc get secrets
  

🔧 Logs and Debugging

- View pod logs:

  oc logs <pod-name>
  

- Open a terminal session in a pod:

  oc rsh <pod-name>
  

- Get events in the project:

  oc get events
  

🔧 Access Control

- Add a user to a project:

  oc adm policy add-role-to-user <role> <user> -n <project-name>
  

- Get current user details:

  oc whoami
  

Keep these commands handy to streamline your DevOps processes in OpenShift! 🌟


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

Getting started with Azure is a great choice for cloud computing. Here are some steps to help you begin:


1. Create an Azure Account:
Go to the Azure free account page and click "Start free."
Sign in using your Microsoft or GitHub account.
Provide your details (name, email, contact number) and verify your identity.
Review and accept the agreement and privacy statement.


2. Explore Azure Services:
Visit the Azure portal.
Use the search bar to find the Quickstart Center or select it from the All services menu.
In the Quickstart Center, explore the tabs:

Get started: Learn the basics of Azure through demos and live Q&A sessions.
Projects and guides: Choose projects and follow step-by-step guides.
Take an online course: Dive deeper into specific topics.


3. Watch How-To Videos:
Check out the Azure videos to learn how to work with Azure services in the portal.


4. Learn from Documentation and Training:
Read the Azure developer guide.
Access Azure documentation, example code, and tutorials for all services.
Follow the Azure Fundamentals online learning path.


5. Start Building:
Create your first solution in Azure using the Azure Quickstart Center.
Explore options like creating virtual machines, building web apps, using Azure SQL Database, and integrating AI services.

Remember, you can enjoy popular Azure services free for 12 months, with more than 55 services free always, and a $200 credit in your first 30 days. Happy exploring! 🚀🌐

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



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

🚀 The Ultimate DevOps Bootcamp Program 2024 Edition by ProDevOpsGuy 🚀


➡️ Bootcamp Program Link: https://blog.prodevopsguy.xyz/the-ultimate-devops-bootcamp-2024-pack-by-prodevopsguy

➡️ Complete DevOps Bootcamp Syllabus: https://blog.prodevopsguy.xyz/the-ultimate-devops-bootcamp-syllabus


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

🌟 Different types of DevOps ♾ and Cloud ☁️ Roles and Their Activities 🌟

🖥 https://blog.prodevopsguy.xyz/different-types-of-devops-and-cloud-roles-and-their-activities


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

🔥 DevOps Project-20: Azure DevOps pipeline + Terraform Deployment Tutorial ♾


🔗 Project Link: HERE

🔄 Project Overview :-
This guide will cover everything required to deploy an example Azure Service Bus instance via Terraform and ADO.

👉 In addition to creating an example pipeline, we'll also add enhanced capabilities, including -
✅ Hosting the Terraform backend state on Azure blob storage
✅ Creating a deployment Service Principal + setting RBAC permissions on the Azure subscription
✅ Create a multi-stage ADO pipeline with an approval step
✅ Demonstrating how we can scale with multiple deployments


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

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


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

⭐️ https://roadmap.sh/devops


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

Horizontal vs Vertical Scaling 🚀


➡️ Horizontal Scaling (Scaling Out)
Instead of upgrading a single machine, we add more machines or servers to share the load.

✅ Some benefits of horizontal scaling are: helps us to enhance reliability (no single point of failure), better load distribution, simple to implement, costs less, fewer points of downtime.


➡️ Vertical Scaling (Scaling Up)
We upgrade our existing servers/machines with more powerful hardware such as more memory, CPU, storage, etc.

✅ Some benefits of vertical scaling are: are simple to manage (fewer servers to handle), faster performance for specific tasks, and no need to reconfigure systems for multiple servers, less complicated maintenance.


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

Monitor Data Transfer with Pipe Viewer (pv) 🚀

Imagine migrating a website and manually transferring data from a local SQL file (around 450MB) to a new MySQL database hosted on a managed service like RDS.

We can use the Pipe Viewer (pv) utility to track the progress.

- pv, or Pipe Viewer, is a command-line tool that allows you to monitor data transfer progress within your terminal.
- pv can be inserted into any data transfer pipeline between two processes.

➡️This provides valuable insights such as:
- Transfer speed
- Elapsed time
- Completion percentage
- Estimated time remaining

𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Here's a command demonstrating how to use pv during an import:

pv backup.sql | mysql -h rds-amazonaws-com -u <user-name> -p <db-name>

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

📣 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