Real-Time DevOps Project Using Kubernetes

Подписаться 773

Просмотров 13 тыс.

50% 1

Special thanks to @cloudacademydevops for the docker images and my fellow youtuber @cloudchamp for awesome implementation docs.
Welcome to our Kubernetes Live Project! In this real-time DevOps project, we will guide you through the process of deploying a cloud-native Voting application using microservices on a Kubernetes Cluster from scratch. This project is an excellent addition to your DevOps portfolio and will help you showcase your skills on your resume.
GitHub Repository: github.com/sek...
Project Highlights:
Set up an EKS (Elastic Kubernetes Service) cluster from the ground up.
Deploy a fully functional application consisting of:
Frontend built in React (compiled in a container image).
API implemented in Golang (compiled in a container image).
MongoDB as a database with replicaset for high availability.
Comprehensive step-by-step instructions for beginners and experienced DevOps professionals alike.
Learn how to test the application within the Kubernetes environment.
Why You Should Watch:
This Kubernetes project provides hands-on experience in deploying a complex application on Kubernetes, making it a valuable addition to your DevOps skillset. Whether you're a beginner looking to learn Kubernetes or an experienced professional looking to expand your portfolio, this project has something for everyone.
Don't forget to star our GitHub repository and subscribe to our channel for more exciting DevOps and Kubernetes projects. Get ready to enhance your DevOps expertise and elevate your resume with this real-time project!
#DevOpsProject #Kubernetes #AWS #EKS (Elastic Kubernetes Service) #Microservices #CloudNative #Containers #ContinuousIntegration #ContinuousDelivery #SiteReliabilityEngineering #Docker #GitHub #DevOpsLife #InfrastructureAsCode #Automation #Containerization #CloudComputing #GitOps #K8s (Kubernetes shorthand) #DevOpsSkills #CI/CD #KubernetesCluster #CloudDeployment #DevOpsJourney #DeploymentPipeline #EKS2023 #nepal #nepaltech #devops #SRE #devopsnepal #cloudcast #cloudcastnepal #nepaltech #devops #devsecops #nepaltechtube #SRE #tech #cloudcastnepal

Опубликовано:

29 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 14

@Cloudcastnepal 8 месяцев назад

Did you try this ?

@Courtofsachin 7 месяцев назад

Useful video 😊

@amitdahat1750 10 месяцев назад

Excellent. Waiting for aws Serverless service

@MadhanKumar-zj6kn 10 месяцев назад

Excellent 👍👌

@anilkommalapati6248 8 месяцев назад

Nice demo and really useful for beginners. A small doubt here: After creating EKS cluster , from the control plane/Client machine to connect to the EKS cluster don't we need to copy the "kubeconfig" file into .kube/config folder ??

@Cloudcastnepal 8 месяцев назад

aws eks update-kubeconfig --name cluster-name --region us-east-2 running the “aws eks update-kubeconfig” command sets the context for your Kubernetes configuration to interact with the specified Amazon EKS cluster. It essentially updates your local kubeconfig file with the necessary information, similar to manually copying kubeconfig.

@user-yu9ky6xh9n 9 месяцев назад

Hi Nicely explained but I have one question. For api-deployment instead of service of type LB why don't you use cluster IP service ??

@hungrysaoji9918 9 месяцев назад

API server needs to access the internet from outside. Cluster IP service creates a connection between pods inside a cluster by providing a virtual IP address. However, cluster IP does not provide access to the outside world. Therefore for pods to access the internet and be controlled from outside they used the service LB for API

@prabhawsoti9896 7 месяцев назад

Can you make video on best way to create dockerfile and docker compose new way so change will reflect realtime in springboot kotlin grader- kotlin,

@meetsirnel 9 месяцев назад

Awesome project. How can one do this using kubeadm 😮

@Cloudcastnepal 9 месяцев назад

Setup Kubernetes cluster using kubeadm: 1. Prerequisites: Prepare multiple Linux nodes, install a container runtime, and disable swap. 2. Install Kubernetes Tools: Install kubeadm, kubectl, and kubelet on all nodes. 3. Initialize the Control Plane Node: Run kubeadm init on one node to initialize the control plane. 4. Set Up Cluster Networking: Install a Pod network add-on to enable Pod communication. 5. Join Worker Nodes: Use the kubeadm join command on worker nodes to join the cluster. 6. Copy Kubernetes Configuration: Copy the Kubernetes configuration from the control plane node to your local machine. 7. Verify the Cluster: Use kubectl to check node status with kubectl get nodes. 8. Deploy Applications: Deploy applications and services using kubectl apply. 9. Optional Add-Ons: Install additional tools and add-ons like monitoring and logging as needed.

@Nerddog12344 10 месяцев назад

Why not nodeport is used for service(mongo)?

@Cloudcastnepal 10 месяцев назад

@athulraju1252 In Kubernetes, the choice between using ClusterIP and NodePort for exposing services like MongoDB depends on your specific use case and security requirements. ClusterIP: ---------------- ClusterIP is typically used when you want to expose a service internally within the Kubernetes cluster. It provides a stable, internal IP address that other pods within the cluster can use to access the service. It is suitable for scenarios where you have applications running within the cluster that need to communicate with the MongoDB service but don't need to be accessible from outside the cluster. ClusterIP is more secure because it doesn't expose the service to the public internet or external networks. NodePort: ---------------- NodePort, on the other hand, exposes a service on a static port on each Node's IP address. This makes the service accessible externally, outside of the Kubernetes cluster, via any Node's IP address on the specified port. NodePort is used when you need to expose a service to external clients or applications that are not running within the Kubernetes cluster. It's commonly used for applications that need to be accessible over the internet or from other non-Kubernetes environments. NodePort is less secure because it exposes the service to the external network, which may require additional security measures like firewalls or authentication mechanisms. Ultimately, the choice between ClusterIP and NodePort depends on your specific networking and security requirements for your MongoDB deployment within Kubernetes.

@hungrysaoji9918 9 месяцев назад

Through Nodeport a port number between (30000 to 32700) gets assigned to the entire cluster and then we can access the database from the browser through the public IP of the Ec2 instance and port no. (ip:port-number). We do not want someone to access the database from outside. Therefore cluster IP has been assigned to the cluster so that communication can be made between pods only but not from the outside world. Please check this video for a clear and brief explanation of Kubernetes networking. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-J2sUlm2cwQk.html