Скачать с ютуб 15. Master KUBERNETES Deployment Strategies: Rolling Updates, Rollbacks, Recreate & Replicas в хорошем качестве

15. Master KUBERNETES Deployment Strategies: Rolling Updates, Rollbacks, Recreate & Replicas

In this video, I dive deep into key Kubernetes deployment strategies: rolling updates, rollbacks, recreate, and managing replicas. Understanding these concepts is crucial for ensuring smooth and reliable application deployment in a Kubernetes cluster. Rolling updates allow you to incrementally update your application without downtime, gradually replacing old versions of pods with new ones. This ensures that users don’t experience disruptions as the new version is rolled out. Rollback provides a safety net in case something goes wrong during a deployment. With a simple command, you can roll back to a previous stable version of your application, restoring service quickly. Recreate is a more aggressive strategy, where the existing pods are terminated before new ones are created. While it’s effective for certain use cases, it can cause temporary downtime, making it less suitable for production environments that require high availability. Replicas in Kubernetes ensure that the desired number of pod instances are running at any given time, providing fault tolerance and scalability. Throughout the video, I compare these approaches in depth, showing the benefits and potential drawbacks of each. Additionally, I demonstrate these strategies with practical examples in a live lab environment, so you can see them in action and understand how to implement them in your own Kubernetes clusters. Below is a sample Kubernetes manifest file showcasing a rolling update deployment: apiVersion: apps/v1 kind: Deployment metadata: name: myapp-deployment labels: app: nginx spec: replicas: 3 selector: matchLabels: type: front-end template: metadata: name: myapp-pod labels: app: myapp type: front-end spec: containers: name: nginx-container image: nginx:1.7.1 kubectl apply -f deployment-definition.yaml kubectl set image deployment/myapp-deployment nginx=nginx:1.9.1 apiVersion: apps/v1 kind: Deployment metadata: name: myapp-deployment spec: replicas: 3 strategy: type: Recreate selector: matchLabels: app: myapp template: metadata: labels: app: myapp spec: containers: name: myapp-container image: nginx:1.18.0 apiVersion: apps/v1 kind: Deployment metadata: name: myapp-deployment labels: app: nginx spec: template: metadata: name: myap-pod labels: app: myapp type: front-end spec: containers: name: nginx-container image: nginx:1.7.1 replicas: 3 selector: matchLabels: type: front-end command for updating the image kubectl set image deployment/myapp-deployment nginx-container=nginx:1.9.1 First, create a deployment with the initial version of the image. apiVersion: apps/v1 kind: Deployment metadata: name: myapp-deployment labels: app: nginx spec: replicas: 3 selector: matchLabels: app: myapp template: metadata: labels: app: myapp spec: containers: name: nginx-container image: nginx:1.7.1 # Initial version kubectl apply -f deployment.yaml kubectl set image deployment/myapp-deployment nginx-container=nginx:1.9.1 kubectl rollout status deployment/myapp-deployment kubectl rollout history deployment/myapp-deployment kubectl rollout undo deployment/myapp-deployment kubectl rollout undo deployment/myapp-deployment --to-revision=1 kubectl rollout status deployment/myapp-deployment #Kubernetes #K8s #DevOps #KubernetesTutorial #KubernetesDeployment #CloudComputing #ContainerOrchestration #RollingUpdate #Rollback #KubernetesRollingUpdate #KubernetesRollback #KubernetesRecreate #ReplicasInKubernetes #Microservices #CI_CD #KubernetesCluster #KubernetesBestPractices #CloudNative #DockerKubernetes #KubernetesLab #TechTutorial #KubernetesAutomation #TechEducation #KubernetesForBeginners #clouddevops