-
Notifications
You must be signed in to change notification settings - Fork 375
feat(kubernetes): create guide about migration about external #8124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
To successfully migrate your Kubernetes cluster to OVHcloud, ensure you have the following in place: | ||
|
||
- **Velero Setup:** Velero, along with its Helm chart, should be installed and configured on your source Kubernetes cluster. It's crucial that Velero is connected to an OVHcloud S3-compatible Object Storage endpoint for backup storage. You can find detailed instructions for Velero installation and configuration in the official [Velero Helm chart documentation](https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/README.md){.external}. | ||
- **OVHcloud S3-compatible Endpoint:** Ensure your Velero setup correctly references the OVHcloud S3-compatible endpoints as the BackupStorageLocation. If you encounter any difficulties with these settings, don't hesitate to reach out to our [Professional Services experts](https://www.ovhcloud.com/en-gb/professional-services){.external} for assistance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we need to provide more than a 'contact professional service'. There is an existing MKS and Velero doc that we can rely on for the s3 configuration : https://help.ovhcloud.com/csm/fr-public-cloud-kubernetes-backing-up-cluster-velero?id=kb_article_view&sysparm_article=KB0054867
- **Replicate network setup:** Ensure your new cluster's network configuration mirrors your original cluster (e.g., private nodes on a private subnet, dedicated outbound gateway). | ||
- **Choose deployment mode:** Select a deployment mode (e.g., 1AZ or 3AZ) based on your fault tolerance needs and high availability requirements. | ||
|
||
3. **Create your target Kubernetes cluster on OVHcloud** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
step 2 and 3 should be inverted ? Creation a cluster then select a flavor
|
||
4. **Deploy Velero Helm chart on the new cluster** | ||
|
||
- On your newly created OVHcloud Kubernetes cluster, deploy the Velero Helm chart. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What type of Pull Request is this?
Description
Refer to SK-2211
Mandatory information