https://prodevopsguy.github.io/2024/Ultimate-DevOps-Bootcamp-2024-Pack/

⚠️ Note: Anyone Interested, can open the Blog 🌐, share it to your friends and colleagues.


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

🧑‍💻 Git/GitHub 🆓 Videos :-

〰️ https://drive.google.com/drive/folders/1vhSsxz9oAtSh136JVo3gryaDPJAYWteF?usp=sharing


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

🪙 Openshift 🆓 Videos :-

➡️ https://drive.google.com/drive/folders/1jBbTglBbFOp4bEO08HEuhUjcE18qXuZo?usp=sharing


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

💳 Ansible 🆓 Videos :-

➡️ https://drive.google.com/drive/folders/1p35HHSamOyL1Rta8hK5--4k1mPWYAXaV?usp=sharing


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

➡️Docker 🐬 and Kubernetes Free Videos 🟩 :

✅Link: https://drive.google.com/drive/folders/162YOHhybk_pYemCfKmKSGbdSjJDeuAYR?usp=sharing


❤️ Follow for more: @prodevopsguy

💥 DevOps Roadmap 2024 ☄️

🚀 Exciting Tech Talk! ✨

Unlock the Power of Automation with Ansible! 🌐💻

📌 Ansible, the ultimate IT automation tool, brings efficiency to your tasks with these key features:
🔢 IT Automation
🔢 Configuration Management
🔢 Automated Deployment

🛠 Dive into the Pool Configuration Tool:

➡️ Nodes: Systems waiting to be configured and regularly check with the server and fetch configurations.
➡️ Module: Your configuration code file
➡️ Inventory: A handy document grouping nodes under specific labels

📘 Master the Playbook:
- The core of Ansible, a set of instructions to configure nodes.
- Written in YAML for simplicity and flexibility.

📊 Meet the Inventory:
- a. Webserver
- b. Database server

🌐 Elevate with Ansible Tower by Red Hat:
- A framework that enriches Ansible.
- Provides a sleek GUI, reducing dependency on the 'cmd' window.

🚀 Streamline your operations, automate with Ansible! 💪💡


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

https://harshhaa.hashnode.dev/devsecops-deploying-the-2048-game-on-docker-and-kubernetes-with-jenkins-cicd

Follow 🍩 Like 👍 Share 👍 Comment Your thoughts 💬

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

🤖 𝗧𝗼𝗽 𝗔𝗜 𝗧𝗼𝗼𝗹𝘀 𝗳𝗼𝗿 𝗗𝗲𝘃𝗢𝗽𝘀 𝗶𝗻 𝟮𝟬𝟮𝟰

🔢. Kubiya
🔢. Amazon CodeGuru
🔢. Sysdig

🔢. PagerDuty
🔢. Atlassian Intelligence
🔢. Dynatrace’s Davis

🔢. Datadog APM
🔢. Snyk
🔢. Harness


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

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

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


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

How to Get Into DevOps?

There isn't a one-size-fits-all path to DevOps.

If you come from a background in development, QA, performance, or support, you should focus on learning about the Cloud, infrastructure automation, container orchestration, and CI/CD.

Most importantly, you must work on real-world use cases.

If you are a fresher, you must concentrate on IT fundamentals, programming, OS concepts, Cloud, and Containers.

Getting a job in the DevOps domain as a newcomer can be challenging. Internships are a good starting point.

This is because most companies (primarily service-based) seek experienced individuals who can immediately contribute to projects.

As the well knowledged person, I've noticed that clients always prefer hiring experienced professionals.

Dedicate yourself to learning and avoid shortcuts.

With hard work, luck will naturally come your way. ☺️


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

😀 A Kubernetes service is a 𝗹𝗼𝗴𝗶𝗰𝗮𝗹 𝗰𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻 𝗼𝗳 𝗽𝗼𝗱𝘀 in a Kubernetes cluster and 𝗲𝗮𝘀𝗶𝗹𝘆 𝗲𝘅𝗽𝗼𝘀𝗲 𝗮𝗻 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 deployed on a set of pods using a single endpoint.

➡️ If a service is keeping track of pods 𝘂𝘀𝗶𝗻𝗴 𝗹𝗮𝗯𝗲𝗹𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗜𝗣 𝗮𝗱𝗱𝗿𝗲𝘀𝘀 and the label is always the same.

➡️ Labels are the 𝗽𝗿𝗼𝗽𝗲𝗿𝘁𝗶𝗲𝘀 attached to each item/object. Selector helps us to 𝗳𝗶𝗹𝘁𝗲𝗿 𝘁𝗵𝗲 𝗶𝘁𝗲𝗺𝘀/objects which have labels attached to them.

➡️ Each Pod gets its 𝗼𝘄𝗻 𝗶𝗻𝘁𝗲𝗿𝗻𝗮𝗹 𝗜𝗣 𝗮𝗱𝗱𝗿𝗲𝘀𝘀, but the Pods in K8s are ephemeral, meaning that they are destroyed frequently.

➡️ Pod restarts or when old one dies and the new one gets started in its place it 𝗴𝗲𝘁𝘀 𝗮 𝗻𝗲𝘄 𝗜𝗣 𝗮𝗱𝗱𝗿𝗲𝘀𝘀.

➡️ YAML is a human-friendly language. In the context of Kubernetes, YAML files are 𝗺𝗮𝗶𝗻𝗹𝘆 𝘂𝘀𝗲𝗱 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗰𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻 of K8 pods, services, and deployments.

In Kubernetes, YAML is a manifest file.

➡️ 𝗣𝗼𝗿𝘁 --> exposes the Kubernetes service on the 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗲𝗱 𝗽𝗼𝗿𝘁 𝘄𝗶𝘁𝗵𝗶𝗻 𝘁𝗵𝗲 𝗰𝗹𝘂𝘀𝘁𝗲𝗿. Other pods within the cluster can communicate with this server on the specified port.

➡️ 𝗧𝗮𝗿𝗴𝗲𝘁𝗣𝗼𝗿𝘁 --> This is the port on the pod that the request gets 𝘀𝗲𝗻𝘁 𝘁𝗼 𝘆𝗼𝘂𝗿 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝗯𝗲 𝗹𝗶𝘀𝘁𝗲𝗻𝗶𝗻𝗴 𝗳𝗼𝗿 𝗻𝗲𝘁𝘄𝗼𝗿𝗸 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀 𝗼𝗻 𝘁𝗵𝗶𝘀 𝗽𝗼𝗿𝘁 for the service to work.

💢 Services 💢
☑️ Load Balancing
☑️ Service Discovery
☑️ Expose to external world --> Outside K8's cluster

💢 Service types 💢
☑️ Cluster IP - Only accessible from within the cluster
☑️ Node port - Static port on each node’s IP
☑️ Load balancer - Cloud provider’s load balancer


❤️ Follow for more: @prodevopsguy

🔼🔽 Software Development Lifecycle


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

📣 Hiring for DevOps - SRE

Role for leading IT Firm in Bangalore with 2 to 4 Years of experience in AWS, EKS , Cluster Creation and deployment

Interested?

✉️ Mail at mitalin@symphonihr.com

📣 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝗶𝗲𝘀 𝗼𝗳 𝗮 𝗗𝗲𝘃𝗢𝗽𝘀 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿? ✨

✔️𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻: Fostering cross-functional collaboration between development, operations, and other stakeholders to ensure alignment of goals and priorities.

✔️𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻: Designing, implementing, and maintaining automated processes for CI/CD pipelines, infrastructure provisioning, configuration management, and testing.

✔️𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: Managing infrastructure resources using IaC tools like Terraform or CloudFormation, optimizing scalability, performance, and cost-efficiency.

✔️𝗧𝗼𝗼𝗹𝗶𝗻𝗴 𝗮𝗻𝗱 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻: Identifying, evaluating, and integrating DevOps tools and technologies to improve productivity, such as version control systems, CI/CD platforms, and container orchestration tools.

✔️𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆: Establishing monitoring solutions to track system performance, detect anomalies, and facilitate timely resolution of issues. Implementing logging mechanisms for centralized log aggregation and analysis.

✔️𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗮𝗻𝗱 𝗖𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲: Integrating security best practices into the development pipeline, implementing security controls, performing vulnerability assessments, and ensuring compliance with regulatory requirements.

✔️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁: Analyzing workflows, identifying bottlenecks, and implementing process improvements to enhance efficiency, reliability, and time-to-market.

✔️𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀: Implementing deployment strategies like canary releases, blue-green deployments, or feature flagging to minimize downtime and mitigate risks during software releases.

✔️𝗜𝗻𝗰𝗶𝗱𝗲𝗻𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: Developing incident response plans, coordinating responses to production incidents, conducting post-incident reviews, and implementing preventive measures to minimize recurrence.

✔️𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻: Identifying performance bottlenecks, optimizing system configurations, and tuning application components to improve overall system performance and scalability.

✔️𝗖𝗮𝗽𝗮𝗰𝗶𝘁𝘆 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴:Forecasting resource requirements based on workload trends, analyzing utilization patterns, and scaling infrastructure resources to meet evolving business needs.

✔️𝗗𝗶𝘀𝗮𝘀𝘁𝗲𝗿 𝗥𝗲𝗰𝗼𝘃𝗲𝗿𝘆: Designing and implementing disaster recovery plans, ensuring data integrity, and minimizing recovery time objectives (RTO) and recovery point objectives (RPO) in the event of system failures or outages.

DevOps engineers play a critical role in driving collaboration, automation, and efficiency across development and operations teams, ultimately enabling organizations to deliver high-quality software products and services more rapidly and reliably.

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

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

💥 Tool Agnostic CI/CD: Building Pipelines that Adapt and Thrive 💥


Here's how you can break free from tool dependence and create a CI/CD pipeline that adapts and thrives:

1⃣. 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝘁𝗵𝗲 𝗣𝗿𝗼𝗰𝗲𝘀𝘀, 𝗡𝗼𝘁 𝘁𝗵𝗲 𝗧𝗼𝗼𝗹𝗯𝗼𝘅:
- Define your 𝗰𝗼𝗿𝗲 𝗖𝗜/𝗖𝗗 𝘀𝘁𝗮𝗴𝗲𝘀: code building, testing, deployment, and monitoring.
- Understand the "𝘄𝗵𝘆" 𝗯𝗲𝗵𝗶𝗻𝗱 𝗲𝗮𝗰𝗵 𝘀𝘁𝗮𝗴𝗲 𝗮𝗻𝗱 𝗶𝘁𝘀 𝗱𝗲𝘀𝗶𝗿𝗲𝗱 𝗼𝘂𝘁𝗰𝗼𝗺𝗲.
- Don't get bogged down in specific tool features; focus on the overall workflow.

2⃣. 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗮𝘀 𝗖𝗼𝗱𝗲 (𝗜𝗮𝗖):
- Use IaC tools like Terraform or Ansible to 𝗱𝗲𝗳𝗶𝗻𝗲 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗰𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗰𝗼𝗱𝗲.
- This makes your pipeline 𝗽𝗼𝗿𝘁𝗮𝗯𝗹𝗲 𝗮𝗻𝗱 𝗶𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝘁 𝗼𝗳 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗰𝗹𝗼𝘂𝗱 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿𝘀 𝗼𝗿 𝗽𝗹𝗮𝘁𝗳𝗼𝗿𝗺𝘀.
- Changes are easily tracked and versioned, ensuring consistency and repeatability.

3⃣. 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀 𝗳𝗼𝗿 𝗣𝗼𝗿𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆:
- Package your applications in containers using Docker or similar technologies.
- Containers run consistently across different environments, making deployment flexible and reliable.
- You can focus on building and testing within containers, independent of the target environment.

4⃣. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝗢𝗽𝗲𝗻 𝗦𝘁𝗮𝗻𝗱𝗮𝗿𝗱𝘀 𝗮𝗻𝗱 𝗔𝗣𝗜𝘀:
- Choose tools that integrate seamlessly with open standards and APIs like Docker Hub or Kubernetes.
- This opens up a wider range of compatible tools and services in the future.
- Avoid vendor lock-in and maintain flexibility to switch tools if needed.

5⃣. 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗦𝘁𝗿𝗼𝗻𝗴 𝗧𝗼𝗼𝗹𝗰𝗵𝗮𝗶𝗻 𝗙𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻:
- Select core tools for specific tasks (e.g., version control, testing frameworks).
- Ensure they are widely adopted and have strong communities for support and updates.
- Choose tools with good documentation and active development to future-proof your pipeline.

6⃣. 𝗙𝗼𝘀𝘁𝗲𝗿 𝗮 𝗖𝘂𝗹𝘁𝘂𝗿𝗲 𝗼𝗳 𝗘𝘅𝗽𝗲𝗿𝗶𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻:
- Don't be afraid to try different tools and workflows within your tool-agnostic framework.
- Encourage collaboration and knowledge sharing among team members.
- Continuously iterate and refine your pipeline based on results and feedback.

➡️ 𝗥𝗲𝗺𝗲𝗺𝗯𝗲𝗿: Building a tool-agnostic CI/CD pipeline is not about avoiding tools altogether. It's about 𝘂𝘀𝗶𝗻𝗴 𝘁𝗵𝗲𝗺 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰𝗮𝗹𝗹𝘆 𝘄𝗶𝘁𝗵𝗶𝗻 𝗮 𝘄𝗲𝗹𝗹-𝗱𝗲𝗳𝗶𝗻𝗲𝗱 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸. This approach empowers you to adapt to changing technologies, embrace innovation, and build pipelines that deliver true value.


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