Resetting an OVHcloud Managed Kubernetes cluster
Find out how to reset an OVHcloud Managed Kubernetes cluster
Find out how to reset an OVHcloud Managed Kubernetes cluster
Last updated March 23rd, 2023.
OVHcloud Managed Kubernetes service provides you Kubernetes clusters without the hassle of installing or operating them.
Through the OVHcloud Control Panel and the API, you can reset your OVHcloud Managed Kubernetes cluster.
During a reset, all data in the ETCD will be deleted (pods, deployments, services, secrets, CRDs, etc.). Similarly, load balancers and also all PVC (Persistent Volume Claim) with their PCI cinder volumes will be deleted. Nodes will be either deleted or reinstalled (depending on the option you set during the reset).
The whole cluster configuration is reset but some values can be defined (optional):
Log in to the OVHcloud Control Panel, go to the Public Cloud
section and select the Public Cloud project concerned.
Access the administration UI for your OVHcloud Managed Kubernetes clusters by clicking on Managed Kubernetes Service
in the left-hand menu.
Click on your Kubernetes cluster.
In the Service tab of the administration UI, click on Reset your cluster.
You have two options on the reset menu, Delete and Reinstall.
Choosing Delete nodes means that the current cluster nodes are deleted, and the cluster is reinitialized to an empty state.
Choosing Keep and reinstall nodes means that the cluster is reinitialized without destroying the nodes.
You can also choose the minor version of the cluster and the private network attached.
Click on the Confirm
button to continue.
Depending on the chosen kind of reset, the process can take several minutes. During that time, a message on the manager warns you that the cluster is under resetting:
To simplify things, we are using the API Explorer which allows to explore, learn and interact with the API in an interactive way.
Log in to the API Explorer using your OVHcloud NIC handle.
If you go to the Kubernetes section of the API Explorer, you will see the available endpoints:
Input:
{
"name": "my-test-cluster",
"updatePolicy": "ALWAYS_UPDATE",
"version": "1.25"
}
Result:
null
By default, if you don't specify it, the workerNodesPolicy
option will be equivalent to delete
. If you don't want your Nodes deleted but reinstalled instead, you have to specify "workerNodesPolicy": "reinstall"
.
You should receive a response with null
content. This message will be improved in the future with the same information you have after a Kubernetes cluster creation.
Result:
{
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
"region": "GRA5",
"name": "my-test-cluster",
"url": "xxxxxx.xx.gra.k8s.ovh.net",
"nodesUrl": "xxxxxx.nodes.c1.gra.k8s.ovh.net",
"version": "1.25.4-2",
"nextUpgradeVersions": [],
"kubeProxyMode": "iptables",
"customization": {
"apiServer": {
"admissionPlugins": {
"enabled": [
"AlwaysPullImages",
"NodeRestriction"
],
"disabled": []
}
}
},
"status": "REDEPLOYING",
"updatePolicy": "ALWAYS_UPDATE",
"isUpToDate": true,
"controlPlaneIsUpToDate": true,
"privateNetworkId": null,
"createdAt": "2023-03-21T10:53:35Z",
"updatedAt": "2023-03-22T09:16:34Z"
}
To have an overview of OVHcloud Managed Kubernetes service, you can go to the OVHcloud Managed Kubernetes page.
Otherwise to skip it and learn more about using your Kubernetes cluster the practical way, we invite you to look at our tutorials.
Join our community of users.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community