Configuring and updating
-
What should I do if I lose some of my data during a Kubernetes version upgrade?
-
Will my resources be unavailable while Kubernetes is going through a version upgrade?
-
Can I upgrade my Managed Service for Kubernetes cluster in one step?
-
Can I send you a YAML configuration file so that you apply it to my cluster?
-
What should I do if volumes fail to attach after a Kubernetes upgrade?
What should I do if I lose some of my data during a Kubernetes version upgrade?
Your data will not get lost as Managed Service for Kubernetes creates a data backup prior to upgrading the Kubernetes version. You can manually configure cluster backup in Yandex Object Storage. We also recommend using the application's native features to back up your databases.
Can I configure a backup for a Kubernetes cluster?
Yandex Cloud provides secure storage and replication for data in Managed Service for Kubernetes clusters. However, you can back up data from your Managed Service for Kubernetes cluster node groups at any time and store it in Object Storage or other types of storage.
For more information, see Managed Service for Kubernetes cluster backups in Object Storage.
Will my resources be unavailable while Kubernetes is going through a version upgrade?
When a master is going through an upgrade, control plane resources will experience downtime. For this reason, operations like creating or deleting a Managed Service for Kubernetes node group will be unavailable. Still, the application will continue serving user requests.
If max_expansion is greater than zero, Managed Service for Kubernetes creates new nodes when upgrading node groups. The system moves all workloads to the new nodes and deletes the old node groups. The downtime in this case equals the time it takes for a pod to restart when moved to the new Managed Service for Kubernetes node group.
Can I upgrade my Managed Service for Kubernetes cluster in one step?
It depends on the source and target versions of the Managed Service for Kubernetes cluster upgrade. In one step, you can only upgrade your Managed Service for Kubernetes cluster to the next minor version from the current one. Upgrading to newer versions is done in multiple steps, e.g., 1.19 → 1.20 → 1.21. For more information, see Updating a cluster.
If you want to skip intermediate versions, create a Managed Service for Kubernetes cluster of the version you need and migrate the workloads from the old cluster to the new one.
Is the Container Network Interface plugin upgraded together with the Managed Service for Kubernetes cluster?
Yes. If you are using the Calico and Cilium controllers, they are upgraded along with your Managed Service for Kubernetes cluster. To upgrade your Managed Service for Kubernetes cluster, do one of the following:
- Create a Managed Service for Kubernetes cluster of the version you need and migrate the workloads from the old cluster to the new one.
- Upgrade your Managed Service for Kubernetes cluster manually.
To get timely Managed Service for Kubernetes cluster version upgrades, set up auto upgrading.
Can I send you a YAML configuration file so that you apply it to my cluster?
No. You can use a kubeconfig file to apply the YAML file with cluster configuration on your own.
Can you install Web UI Dashboard, Rook, and other tools?
No. You can install all the required tools on your own.
What should I do if volumes fail to attach after a Kubernetes upgrade?
If you get the following error after a Kubernetes upgrade:
AttachVolume.Attach failed for volume "pvc":
Attach timeout for volume yadp-k8s-volumes/pvc
Update the s3-CSI driver to the latest version.