🔥 I have created this handy diagram that breaks down the key concepts of Kafka in a simple and easy-to-understand way.

🔴 𝗣𝗿𝗼𝗱𝘂𝗰𝗲𝗿:

A Kafka producer is an entity that publishes data to topics within the Kafka cluster. In essence, producers are the sources of data streams, which might originate from various applications, systems, or sensors. They push records into Kafka topics, and each record consists of a key, a value, and a timestamp.

🔴 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿:

A Kafka consumer pulls data from Kafka topics to which it subscribes. Consumers process the data and often are part of a consumer group. In a group, multiple consumers can read from a topic in parallel, with each consumer responsible for reading from certain partitions, ensuring efficient data processing.

🔴 𝗧𝗼𝗽𝗶𝗰:

A topic is a category or feed name to which records are published. Topics in Kafka are multi-subscriber; they can be consumed by multiple consumers and consumer groups. Topics are divided into partitions to allow for data scalability and parallel processing.

🔴 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻:

A topic can be divided into partitions, which are essentially subsets of a topic's data. Each partition is an ordered, immutable sequence of records that is continually appended to. Partitions allow topics to be parallelized by splitting the data across multiple brokers.

🔴 𝗕𝗿𝗼𝗸𝗲𝗿:

A broker is a single Kafka server that forms part of the Kafka cluster. Brokers are responsible for maintaining the published data. Each broker may have zero or more partitions per topic and can handle data for multiple topics.

🔴 𝗖𝗹𝘂𝘀𝘁𝗲𝗿:

A Kafka cluster comprises one or more brokers. The cluster is the physical grouping of one or more brokers that work together to provide scalability, fault tolerance, and load balancing. The Kafka cluster manages the persistence and replication of message data.

🔴 𝗥𝗲𝗽𝗹𝗶𝗰𝗮:

A replica is a copy of a partition. Kafka replicates partitions across multiple brokers to ensure data is not lost if a broker fails. Replicas are classified as either leader replicas or follower replicas.

🔴 𝗟𝗲𝗮𝗱𝗲𝗿 𝗥𝗲𝗽𝗹𝗶𝗰𝗮:

For each partition, one broker is designated as the leader. The leader replica handles all read and write requests for the partition. Other replicas simply copy the data from the leader.

🔴 𝗙𝗼𝗹𝗹𝗼𝘄𝗲𝗿 𝗥𝗲𝗽𝗹𝗶𝗰𝗮:

Follower replicas are copies of the leader replica for a partition. They replicate the leader's log and do not serve client requests. Instead, their purpose is to provide redundancy and to take over as the leader if the current leader fails.

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

➡️ Title: DevOps Engineer
➡️ Location: Remote

➡️ Job Description:

1-3 years of exp in DevOps (AWS/ Azure/ GCP).
Hands-on exp in deploying Kubernetes cluster using ELK/ GKE environment.
Creating CI/CD pipeline using Jenkins.
Using Monitoring tools like Prometheus/ Grafana/ Stack driver.
Docker
Infra Automation scripting
➡️ Send resumes/Contact - careers@suesys.com

Remember that time when everyone was like, "Coding? Nah, DevOps is all about automation, CI/CD, blah-blah." Yeah, me too. In 2020, freshman year, convinced myself I could skip "DSA", "messy code" & just focus on DevOps tools. Big mistake. If you are from a Tier 3 college & genuinely want to do good, learn & earn some good bucks, coding & basic computer science knowledge are good to have.

In 2020, there wasn't much content on DevOps (or could be my algo), but there were few solid senior OPS / DevOps folks whom I followed. In recent times, there has been huge content overload, conflicting advice, and enough acronyms to fill a dictionary. If I were to start in 2023, I would've been lost too.

Why I am sharing this? During my freshman year, I used to follow a guy, from whom I got to know about DevOps. He used to say, "Giving back to the community." In my freshman year, I didn't understand what he meant, but now that I do, I want to share this list of free but best resources/bootcamps you can find online.

1️⃣. DevOps Roadmap by Savinder Puri: https://lnkd.in/d-qTThxi

2️⃣. Computer Networks by Kunal Kushwaha: https://lnkd.in/dWmq_ygr && Git/Github tutorial: https://lnkd.in/dGKHzNYg

3️⃣. Docker by Gourav Shah: https://lnkd.in/dKp6bnEA

4️⃣. Playlist of different tools by Kubesimplify / Saiyam Pathak: https://lnkd.in/dWbEP993

5️⃣. Jenkins by Mukesh Otwani: https://lnkd.in/deXCYGkj

6️⃣. Kubernetes by Abhishek Veeramalla: https://lnkd.in/dA6_mtnh

7️⃣. Cloud by ExamPro / Andrew Brown: https://www.exampro.co/

8️⃣. GoLang by Anthony GG: https://lnkd.in/dwVKg8DG


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

May the pride of being Indian fill your heart with joy and gratitude.

Happy Republic Day to you and your family. 🇮🇳


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

😀 10 DevOps Real time Scenarios. 😀
🚀 Issues as well as their resolutions: 🚀

🔢. Continuous Integration Pipeline Failure and its Resolution.
🔗 https://lnkd.in/g9nBb79u

🔢. Application experiences performance degradation and becomes slow during high-traffic periods and its resolution.
🔗 https://lnkd.in/g9nBb79u

🔢. Deployments are error-prone and inconsistent across different environments and its resolution.
🔗 https://lnkd.in/gE6FYcBz

🔢. The application goes down in production due to an unforeseen issue and its resolution.
🔗 https://lnkd.in/gE6FYcBz

🔢. A security vulnerability is discovered in a component of the application stack and its resolution.
🔗 https://lnkd.in/gPtZ9_Ge

🔢. Production environments start to deviate from their desired configurations over time and its resolution.
🔗 https://lnkd.in/gPtZ9_Ge

🔢. A critical service experiences an outage, impacting users and business operations and its resolution.
🔗 https://lnkd.in/gvTtGYC7

🔢. Communication breakdowns between development and operations teams lead to misunderstandings and delays and its resolution.
🔗 https://lnkd.in/gvTtGYC7

🔢. A major release causes unexpected issues in the production environment.
🔗 https://lnkd.in/gYbFKPrv

🔢🔢. Cloud resource costs are increasing beyond budgeted limits.
🔗 https://lnkd.in/gYbFKPrv


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

🚨 𝐇𝐨𝐰 𝐭𝐨 𝐃𝐞𝐩𝐥𝐨𝐲 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 𝐨𝐧 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐏𝐥𝐚𝐭𝐟𝐨𝐫𝐦𝐬 ⚠️

In the kingdom of container orchestration, Kubernetes reigns supreme, empowering developers and DevOps engineers to deploy, manage, and scale their applications with unparalleled efficiency. To truly harness the power of Kubernetes, understanding the complicated interplay of its various components is paramount.

➡️ 𝐏𝐨𝐝
The Building Block of Kubernetes Applications, It is the fundamental unit of Kubernetes, that encapsulates one or more containers, enabling a cohesive environment for your applications.

➡️ 𝐑𝐞𝐩𝐥𝐢𝐜𝐚𝐒𝐞𝐭𝐬
Maintaining the Desired State of Pods they ensure continuous availability by maintaining the specified number of identical Pods

➡️ 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭𝐬
Directing Pod creation and updates, ensuring consistent application state.
With a Deployment at the end, you can effortlessly define the desired number of replicas, image versions, and other configurations.

➡️ 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬
It acts as a stable network endpoint, providing access to your application from the outside world. It abstracts away the nitty-gritty details of individual Pods, allowing clients to seamlessly connect to your application without the hassle of managing IP addresses.

➡️ 𝐈𝐧𝐠𝐫𝐞𝐬𝐬
Routing Traffic with Precision
It stands as a traffic light, intelligently routing external requests to the appropriate services within your cluster.

➡️ 𝐂𝐨𝐧𝐟𝐢𝐠𝐌𝐚𝐩 𝐚𝐧𝐝 𝐒𝐞𝐜𝐫𝐞𝐭
Keeping Configuration and Secrets Secure. These two essential components safeguard your application's configuration and sensitive information.

➡️ 𝐍𝐚𝐦𝐞𝐬𝐩𝐚𝐜𝐞𝐬
Provide order and clarity in multi-tenant environments, while Service Accounts empower Pods with access privileges.

➡️ 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 𝐀𝐜𝐜𝐨𝐮𝐧𝐭
Empowering Pods with Access Privileges. They empower your application components to interact with the broader Kubernetes ecosystem, enabling them to perform their tasks seamlessly.

➡️ 𝐇𝐨𝐫𝐢𝐳𝐨𝐧𝐭𝐚𝐥 𝐏𝐨𝐝 𝐀𝐮𝐭𝐨𝐬𝐜𝐚𝐥𝐞𝐫𝐬
Horizontal pod Autoscalers dynamically scale Pods based on demand, ensuring optimal performance. Scaling with Demand.

➡️ 𝐃𝐚𝐞𝐦𝐨𝐧𝐒𝐞𝐭𝐬
They are the backbone of system-wide services, ensuring that a designated Pod runs on every node in the cluster. They are the unsung heroes of log collection, monitoring agents, and other critical services.

➡️ 𝐂𝐫𝐨𝐧𝐉𝐨𝐛
Scheduling Recurring Tasks..

The CronJob, empowers you to automate recurring tasks, such as backups, cleanup, and data processing, ensuring that your application remains up-to-date and efficient.

These components, each playing a pivotal role, form the complicated tapestry of Kubernetes deployment and management. By leveraging their capabilities, you can confidently navigate the complexities of container orchestration and unleash the true potential of your applications.

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

⭐️ "He's the Best Kubernetes Admin"⭐️

Ever noticed how our tech heroes often go unsung? Picture this: He's the best Kubernetes admin out there – orchestrating containers like a maestro, ensuring seamless scalability, and keeping the digital cogs turning smoothly. But mention his Kubernetes prowess outside our tech bubble, and it’s like announcing you collect rare stamps at a rock concert. 🎸📜

It's a funny (and sometimes frustrating) truth in tech. The complexities that fascinate us – like the intricate dance of a well-managed Kubernetes cluster – are often Greek to the rest of the world. They don't see the wizardry behind keeping systems robust and responsive. That is, until there's a glitch!
#KubernetesAdmin #UnsungHeroes


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

📣 Title: DevOps Engineer
➡️ Location: Remote
➡️ Job Description:

1-3 years of exp in DevOps (AWS/ Azure/ GCP).
Hands-on exp in deploying Kubernetes cluster using ELK/ GKE environment.
Creating a CI/CD pipeline using Jenkins.
Using Monitoring tools like Prometheus/ Grafana/ Stack drivers.
Docker Infra Automation scripting

💬 Share cv : supraja@codcores.com

🚨 Apply fast limited time only 🚨

𝐃𝐞𝐯𝐎𝐩𝐬: 𝐁𝐫𝐢𝐝𝐠𝐢𝐧𝐠 𝐭𝐡𝐞 𝐆𝐚𝐩 𝐁𝐞𝐭𝐰𝐞𝐞𝐧 𝐂𝐨𝐝𝐞 𝐃𝐫𝐞𝐚𝐦𝐬 𝐚𝐧𝐝 𝐂𝐨𝐝𝐞 𝐑𝐞𝐚𝐥𝐢𝐭𝐲 ✨

👉 In a world of perfect code execution, every line would flow flawlessly from mind to keyboard, like a superhero effortlessly soaring through the skies. But in the real world of software development, we often find ourselves navigating a messier terrain, where the code we plan and the code we actually write can sometimes feel like two different galaxies.

🔹 Enter DevOps, the powerful ally that bridges this gap.

Although the meme is just for fun ending weekend !!


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

📌 How to give new users/dev restricted access to Kubernetes namespaces 📌

As a Kubernetes cluster administrator, this is a task you often deal with daily. Here are the steps you need to follow:

1️⃣ Creating a Private Key and CSR: The user first creates a private key and then a Certificate Signing Request (CSR).

2️⃣ Submitting the CSR to the Kubernetes Admin: The user submits this CSR to the Kubernetes administrator.

3️⃣ Signing the CSR: The Kubernetes admin signs the CSR using the CA server's private key and certificate and then creates a kubeconfig file for that specific user.

4️⃣ Generating the Kubeconfig File for the User: The cluster admin create kubeconfig file for that particular user.

5️⃣Creating a Role for the User: The Kubernetes admin creates a role for the user and assigns the necessary access. For example, they might grant access only to the DevOps namespace.

6️⃣Creating a RoleBinding for the User: The admin creates a RoleBinding to assign this role to the particular user.

✅ Note: In Kubernetes, the cluster itself doesn't inherently recognize concepts like users or groups; instead, it relies on certificates for authentication. When a user attempts to access the cluster, they must provide the appropriate certificate. If the certificate is valid, the user is granted access. The specific actions a user can perform within the cluster are determined by the roles assigned to them, which are defined through Kubernetes' Role-Based Access Control (RBAC) system

✅ NOTE: In most scenarios, Kubernetes administrators do not assign permissions to individual users directly. Instead, permissions are typically assigned to groups. All users within a given group then inherit the permissions associated with that group. This approach streamlines the management of access rights, as it allows administrators to control permissions for multiple users collectively rather than individually

💡 Alternative: Using Kubernetes Built-in Certificates API
Another method involves the Kubernetes admin using the built-in Certificates API for handling CSR requests. Instead of manually signing CSRs, the admin can create and approve CSRs


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

➡️ Company name : Agan’s Software Pvt Ltd
➡️ Vacancies: DevOps -AWS.
➡️ Salary: 3 LPA to 4.8 LPA
➡️ No of Vacancies: 4
➡️ Location: Hyderabad
➡️ Experience: Freshers or Minimum One Year Exp
If interested drop your resume to
✉️ Mail : usha@agans.in
☄️ Immediate joining

📣 Opening for DevOps Engineer

➡️ exp: 1 yr
➡️ immediate joiners
➡️ Location: Noida
➡️ WFO only
➡️ Qualification: B.Tech, M.Tech, MCA

✉️ Interested, drop resume at ashika.tomar@buopso.com

📣 Job Opening - DevOps engineer

➡️ Mobisoft Infotech
➡️ Location :#Pune
➡️ Skills :#Freshersonly #AWS #Devops #Linux
➡️ Notice :90 Days
➡️ Qualification :Any
➡️ Salary :As per company
➡️ Experience :0- 2
🔗 Apply from here - https://lnkd.in/gNcUmgVG

🔔 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐄𝐥𝐞𝐦𝐞𝐧𝐭𝐬 𝐌𝐚𝐩 🗺

A holistic view of 🔑 crucial 😀 Kubernetes elements 💡 providing a realistic glimpse 😀 into the intricate and dynamic nature of this powerful container orchestration 🐳 ecosystem 🇺🇦.

This map is a valuable tool for understanding the different components of Kubernetes and how they work together. It is a must-have resource for anyone who wants to learn about Kubernetes or use it to deploy and manage containerized applications.

➡️ 𝐇𝐞𝐫𝐞 𝐚𝐫𝐞 𝐬𝐨𝐦𝐞 𝐚𝐝𝐝𝐢𝐭𝐢𝐨𝐧𝐚𝐥 𝐩𝐨𝐢𝐧𝐭𝐬 𝐚𝐛𝐨𝐮𝐭 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬:
⭐️ Kubernetes is a powerful container orchestration system that can be used to deploy, manage, and scale containerized applications.
⭐️ Kubernetes is used by a wide range of organizations, from small start-ups to large enterprises.
⭐️ Kubernetes is open source and free to use.
⭐️ Kubernetes is constantly evolving and improving.


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

🐳 𝗘𝘅𝗽𝗹𝗼𝗿𝗶𝗻𝗴 𝗗𝗼𝗰𝗸𝗲𝗿 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 🐳

Are you ready to dive into the world of Docker? 🚀 Let's break down the key components of Docker architecture in a nutshell! 🔍

Docker simplifies application deployment and management, making it a go-to tool for DevOps and developers. 🤝

👨‍💻 𝗗𝗼𝗰𝗸𝗲𝗿 𝗖𝗹𝗶𝗲𝗻𝘁
Think of this as your command center! It's the interface you use to interact with Docker. You send commands to the Docker Client, which then communicates with the Docker Daemon to carry out your requests.

🏠 𝗗𝗼𝗰𝗸𝗲𝗿 𝗛𝗼𝘀𝘁
Your trusty server or virtual machine! This is where the magic happens. Docker Host manages the containers, making sure they run smoothly.

🏛 𝗗𝗼𝗰𝗸𝗲𝗿 𝗥𝗲𝗴𝗶𝘀𝘁𝗿𝘆
Your software library! It's a repository for Docker images. Popular ones include Docker Hub. You can store, share, and access images from here.

🏗 𝗗𝗼𝗰𝗸𝗲𝗿 𝗗𝗮𝗲𝗺𝗼𝗻
This persistent process manages containers on the host. It listens for Docker Client requests, creates, starts, stops, and monitors containers.

📦 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿s
Containers are lightweight, portable, and consistent environments. They package your applications and dependencies, making them easily transferable and reproducible.

🖼 𝗜𝗺𝗮𝗴𝗲𝘀
The blueprints for containers! Images are read-only templates that contain everything needed to run your application. They serve as the basis for creating containers.

📥 𝗗𝗼𝗰𝗸𝗲𝗿 𝗣𝘂𝗹𝗹
Like ordering from a menu! 🍔 Use docker pull to fetch images from Docker Hub or other registries and store them on your host. 🌐

🏃‍♀️ 𝗗𝗼𝗰𝗸𝗲𝗿 𝗥𝘂𝗻
Docker run launches a container from an image, creating an instance you can interact with. Specify ports, volumes, and more to customize your container. 🚢

🔨 𝗗𝗼𝗰𝗸𝗲𝗿 𝗕𝘂𝗶𝗹𝗱
Use docker build to create custom images from a Dockerfile. It's like crafting your own unique containers tailored to your application's needs. 🎨


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

👉 🆘 A comprehensive collection of essential DevOps tools for development, deployment, monitoring, and more. 🆘

🔗 Link: https://github.com/NotHarshhaa/devops-tools 🔗

We Explained Each and Every Tools with Detailed Manner with their official site links 🔫

=> Table of Contents
1. Development Environment Tools
2. Source Code Management
3. Build Tools
4. Continuous Integration Tools
5. Artifact Management Tools
6. Code Analysis Tools
7. Continuous Delivery & GitOps Tools
8. Infrastructure Provisioning Tools
9. Cloud Cost Management Tools
10. Configuration Management Tools
11. Secret Management Tools
12. Config/Service Discovery Tools
13. Containerization Tools
14. Container Orchestration Tools
15. Container Security Tools
16. Policy Management Tools
17. Service Mesh Tools
18. Logging Tools
19. Monitoring & Observability Tools
20. Visualization Tools
21. Internal Developer Platform Tools
22. API Tools
23. Collaboration Tools
24. Backups and Restoration Tools
25. Cloud Providers


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

https://harshhaa.hashnode.dev/deploying-an-application-on-kubernetes-a-complete-guide

Follow 🍩 Like 👍 Share 👍 Comment Your thoughts 💬

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