Skip to content

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

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

OvhValentin
Copy link
Contributor

What type of Pull Request is this?

  • New guide(s)
  • Index categories update

Description

Refer to SK-2211

Mandatory information

  • This Pull Request can be merged as soon as possible.

@OvhValentin OvhValentin self-assigned this Jul 3, 2025
@OvhValentin OvhValentin added the Guide creation The Pull Request contains at least 1 new guide (meta.yaml and index edition needed) label Jul 3, 2025
@OvhValentin OvhValentin marked this pull request as draft July 3, 2025 10:19
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.
Copy link
Contributor

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**
Copy link
Contributor

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Guide creation The Pull Request contains at least 1 new guide (meta.yaml and index edition needed)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants