AWS EKS Cluster Upgrade From v1.28 to v1.29 Using Terraform Without Application Downtime |Kubernetes
HTML-код
- Опубликовано: 17 окт 2024
- ===================================================================
1. SUBSCRIBE FOR MORE LEARNING :
/ @cloudquicklabs
===================================================================
2. CLOUD QUICK LABS - CHANNEL MEMBERSHIP FOR MORE BENEFITS :
/ @cloudquicklabs
===================================================================
3. BUY ME A COFFEE AS A TOKEN OF APPRECIATION :
www.buymeacoff...
===================================================================
The RUclips video titled "AWS EKS Cluster Upgrade From V1.28 to V1.29 Using Terraform Without Application Downtime | Kubernetes" offers a detailed tutorial on upgrading an Amazon Elastic Kubernetes Service (EKS) cluster from version 1.28 to version 1.29 using Terraform. The primary focus is to achieve this upgrade without causing any downtime to the applications running on the cluster.
Key Highlights:
Prerequisites:
1. The video outlines the necessary prerequisites, including an active AWS account, an existing EKS cluster on version 1.28, Terraform, and kubectl installed and configured.
Upgrade Strategy: It explains the rolling update strategy to ensure continuous availability of applications during the upgrade process.
Step-by-Step Guide:
1. The video provides a comprehensive step-by-step guide on modifying Terraform scripts to specify the new EKS version, applying the changes, and verifying the upgrade.
2. Verification and Monitoring: Instructions on how to verify the successful upgrade and monitor the cluster’s health post-upgrade.
3. Troubleshooting and Best Practices: The video discusses common issues that might arise, how to troubleshoot them, and best practices for performing upgrades, including taking regular backups and testing in a staging environment.
Learning Objectives:
1. Understand the process of upgrading an EKS cluster using Terraform.
2. Learn how to perform the upgrade without causing application downtime.
3. Gain insights into best practices for managing Kubernetes upgrades in a cloud environment.
4.This video is an excellent resource for DevOps engineers and cloud practitioners aiming to maintain the stability and availability of their Kubernetes applications while performing essential upgrades.
Resources and Links
*Code Repository:* github.com/Rek...
This video serves as a valuable resource for DevOps engineers and cloud practitioners looking to maintain the stability and availability of their Kubernetes applications while performing essential upgrades.
#aws
#eks
#eksupgrade
#kubernetes
#terraform
#awscloud
#cloudcomputing
#devops
#continuousintegration
#continuousdeployment
#cicd
#awsservices
#cloud
#infrastructureascode
#iaas
#zeroapplicationdowntime
#kubectl
#k8s
#kubernetesupgrade
#cloudnative
#awsmanagement
#awsdevops
#kubernetescluster
#terraformeks
#terraformkubernetes
#devopstools
#rollingupdate
#clusterupgrade
#cloudinfrastructure
#clouddeployment
#cloudquicklabs
Hi
Could you suggest if I will do by creating a eks cluster to 1.28 and upgrade the same to 1.29 then how much costing will be for 1 day on free tier any suggestion?
Thank you for watching my videos.
It should negligible as you are choosing free tier EKS nodes.
Thanks for your great efforts, Sir I have a doubt ,From which terraform code I have created the EKS cluster ,Same code I have to use for upgrade can you help please, also could you please make video on Karpenter if it is possible.
Thank you for watching my videos.
Indeed I shall work on that task next.
Hi Sir,
Thanks for making the things easier.
I have a doubt from where you got that result.json and Helppowershell file before updating the cluster?
Thanks!
Thank you for watching my videos.
Please check the video at 5:23 minute you see that I am executing a powershell script which gives the output and stored in results.json.
Hi sir
what is the difference between
EMR Cluster vs EKS Cluster?
Thank you for watching my videos.
EMR : is Elastic Map Reduce which is managed big data processing and analytics service.
EKS: is Elastic Kubernetes Service which is basically managed Kubernetes (container orchestration) Service.
Both are different.
@@cloudquicklabs Okay, hum yahan kah sakte hain ki EMR jo hai, wo Spark aur PySpark ke jobs run karta hai aur EKS jo hai, wo Python ke jobs run karta hai.