Configuring and updating
What do I do if some data gets lost after I update the Kubernetes version?
Your data will not get lost: prior to updating the Kubernetes version Managed Service for Kubernetes creates a data backup. You can manually configure cluster backup in Yandex Object Storage. We also recommend backing up your database using the application tools.
Can I configure a backup for a Kubernetes cluster?
Data in Managed Service for Kubernetes clusters is securely stored and replicated within the Yandex Cloud infrastructure. However, you can back up data from Managed Service for Kubernetes cluster node groups at any time and store them in Object Storage or other types of storage.
For more information, see Managed Service for Kubernetes cluster backups in Object Storage.
Will resources be idle while the Kubernetes version is updating?
When a master is being updated, Control Plane resources will be idle. For this reason, such operations as Managed Service for Kubernetes node group create or delete will be unavailable. User load on the application will continue to be processed.
If the max_expansion value is greater than zero, new nodes are created when Managed Service for Kubernetes node groups are updated. All the load is transferred to new nodes, and the old node groups are deleted. In this case, idle time will be equal to the pod restart time when it is transferred to a new Managed Service for Kubernetes node group.
Can I update a Managed Service for Kubernetes cluster in one step?
It depends on the source and target version you want to migrate your Managed Service for Kubernetes cluster from/to. You can only update your Managed Service for Kubernetes cluster in a single step to the next minor version from the current one. Updating to newer versions is done in steps, e.g., 1.19 → 1.20 → 1.21. For more information, see Updating a cluster.
If you want to skip interim versions, create a Managed Service for Kubernetes cluster of the appropriate version and transfer the load from the old cluster to the new one.
Is the Container Network Interface plugin updated along with a Managed Service for Kubernetes cluster?
Yes, it is. If you are using Calico and Cilium controllers, they are updated along with your Managed Service for Kubernetes cluster. To update your Managed Service for Kubernetes cluster, do one of the following:
- Create a Managed Service for Kubernetes cluster of the appropriate version and transfer the load from the old cluster to the new one.
- Update your Managed Service for Kubernetes cluster manually.
To make sure the current Managed Service for Kubernetes cluster version is updated on time, set up automatic updates.
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 a YAML cluster configuration file on your own.
Can you install Web UI Dashboard, Rook, and other tools?
No. You can install all the necessary tools on your own.
What do I do if I cannot attach volumes after updating Kubernetes?
If the following error occurs after you update Kubernetes:
AttachVolume.Attach failed for volume "pvc":
Attach timeout for volume yadp-k8s-volumes/pvc
Update the s3-CSI driver to the latest version.