Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Subscribe
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Kubernetes Migration | POD Migrated From Cluster 1 to 2
Rating: 3.4 out of 5(2 ratings)
28 students

Kubernetes Migration | POD Migrated From Cluster 1 to 2

Kubernetes Migration | POD Migrated from Kubernetes Cluster 01 to another Cluster with Different Location
Created byTariq J
Last updated 9/2024
English

What you'll learn

  • In this Series , I have covered Kubernetes Migration topic in Which I have migrated resources from One location to another Location
  • I have Migrated POD from Kubernetes Cluster 01 to Another Kubernetes Cluster with different location
  • I Have Used Azure Kubernetes Cluster where i Have Created two Cluster in two Different Location then after i have migrated resources
  • I have covered from scratch level, i have expalin it very well about Architecture of Migration and how do we pre and post palning

Course content

1 section • 9 lectures • 1h 37m total length

  • Kubernetes Migration - Part -017:01
  • Kubernetes Migration - Part -025:15

    Learn how to migrate a pod from one Kubernetes cluster to another using a popular migration tool, including setting up two clusters and applying the migration workflow.

  • Kubernetes Migration - Part -03 - How do we create storage account14:30

    Learn to migrate pods between two Kubernetes clusters by connecting via jump hosts, authenticating, and deploying a sample pod, while creating a storage account and bucket for backup data.

  • Kubernetes Migration - Part -04 - Create Service Principle for authentication16:09
  • Kubernetes Migration - Part -05 - Deploy sample for pod for migration7:48

    Deploy a sample pod across two Kubernetes clusters by applying a corrected pod.yaml in the dev namespace, then validate the yaml and verify pods are running.

  • Kubernetes Migration - Part -06 - Setup Velero Tool On Kubernetes Cluster21:02

    Learn how to set up Velero on two Kubernetes clusters, back up an Argo CD namespace, and migrate resources from cluster one to cluster two using a shared storage account.

  • Kubernetes Migration - Part -07 - Restore Pod to destination Cluster15:00
  • Kubernetes Migration - Part -08 - Take backup and restoration on kubernetes9:58

    Learn how to migrate Kubernetes resources between clusters, back up with Velero, and restore the dev namespace (Jenkins, Tomcat, web app) with troubleshooting via pod logs.

  • Notes1:01

Requirements

  • No Programming experiences needed

Description

In this Series ,  I have covered Kubernetes Migration topic in Which I have Migrated resources from One location to another Location


I have Migrated POD from Kubernetes Cluster 01 to Another Kubernetes Cluster with different location.


I Have Used VELERO tool for Migration.

In this Section I have Explained Architecture Of Migration How we can set up Velero tool in Both Of Cluster.


I Have Used Azure Kubernetes Cluster where i Have Created two Cluster in two Different Location then after i have migrated resources


I have covered from scratch level, i have explain it very well about Architecture of Migration and how do we pre and post Planning


Velero is an open-source tool designed for backup, recovery, and migration of Kubernetes clusters and resources. It enables users to safely back up Kubernetes applications, restore them in case of failure, and migrate them across different clusters. Velero is especially useful in cloud-native environments for disaster recovery and for handling data protection in Kubernetes clusters.

Key Features of Velero:

  1. Backup: Velero allows users to take backups of the entire Kubernetes cluster, including persistent volumes, namespaces, and configurations.

  2. Restore: It provides an easy way to restore applications, clusters, or individual components from a backup.

  3. Disaster Recovery: Velero supports disaster recovery in the event of cluster failures, ensuring business continuity.

  4. Migration: It can move Kubernetes resources and persistent volumes between different clusters or cloud environments.

  5. Scheduling: Users can schedule automatic backups at regular intervals to ensure continuous protection.

  6. Namespace or Resource-Specific Backups: Users can perform targeted backups of specific namespaces, or even individual resources.

Who this course is for:

  • Anyone

Report abuse