Regarding Google Kubernetes Cluster backup

1
votes

I am looking to understand things regarding Google Kubernetes Cluster backup . I came across this document but this seems to be more on GCP Anthos On premises GKE Cluster .

https://cloud.google.com/anthos/gke/docs/on-prem/archive/1.1/how-to/administration/backing-up

I saw few blogs talking of a GKE feature to create a clone of existing GKE Cluster but I cannot find any option in GCP Console to create new cluster by cloning an existing GKE Cluster.

https://blog.doit-intl.com/google-kubernetes-engine-cluster-migration-with-velero-4a140b018f32

Can somebody please confirm if this cloning feature is still available in GKE or it is deprecated ?

Apart from Cloning a GKE Cluster , we need to take backup of Cluster resources and PersistentVolumes. It seems Veloro is a useful tool for this and it is GKE aware.

https://velero.io/

I am looking for further suggestions regarding GKE Cluster backup which takes care of both Cluster resources and persistent volumes. Any recommendation/best practises from Google on GKE backup

1
kubernetesgoogle-cloud-platformbackupgoogle-kubernetes-engine

1 Answers

1
votes

I saw few blogs talking of a GKE feature to create a clone of existing GKE Cluster but I cannot find any option in GCP Console to create new cluster by cloning an existing GKE Cluster.

Can somebody please confirm if this cloning feature is still available in GKE or it is deprecated ?

You can in fact create a duplicate! By going into:

  • Cloud Console (Web UI) -> Kubernetes Engine -> CLUSTER-NAME -> Duplicate.

DUPLICATE

Disclaimer!

This option will create a duplicate of your cluster but it will not copy the workload (Pods, Deployments, Services, Persistent Volumes, etc.)

Transferring your workload will heavily depend on the resources that you are using. You will need to carefully consider all of the resources and choose the solution most appropriate to your use case.

Solution mentioned in the question:

Storage specific:

It could be beneficiary to add that you could also take a different approach and use tools that are designed to provision resources multiple times. Once created "scripts" could be used multiple times (on multiple clusters when migrating etc.). Examples of such tools:

Additional resources: