CCE - Kubernetes 1.19.10, new Everest and CoreDNS version

Cloud Container Engine supports now Kubernetes version 1.19.10 and contains the relevant security improvements from the Kubernetes community. The details of the Kubernetes version 1.19.10 can be found on the Github page. We recommend upgrading your worker nodes by using the rolling upgrade function - see the documentation in the "Performing Rolling Upgrade for Nodes" section. 

Remove and scheduling settings

A new feature in CCE is the Remove and Scheduling settings function. The Remove function allows the reinstallation of the worker node and should be scheduled at off-peak hours to avoid impacting your services. During the removal process, the node is set to Unschedulable status and the pods will be migrated to another worker-node. This function allows you to keep the instance as a normal ECS-node in the same tenant. 

The behaviours of the remove function:

• Compared to the Delete function, the nodes will not be terminated and are kept as normal ECS nodes in the tenant
• The LVM partitions will be cleared and the data should be backed up beforehand
• A KeyPair can be selected during the removal process

The Schedule Settings function affects the availability of the nodes and influences where the workload runs. The function allows switching between the status "schedulable" and "unschedulable". You can find more information about Kubernetes taint on the Kubernetes page.

Other improvements of the CCE release are:

• The new CoreDNS version 1.17.7 corresponds to CoreDNS community version 1.8.4
• The new Everest version 1.2.8 supports:
  • custom AK/SK for OBS volume mount to configure different permissions for individual IAM users
  • default mount options for SFS and OBS storage in a PV or in combination with a StorageClass

The next Kubernetes version 1.21 will be released in a few months.

Further information can be found in the CCE area of the Help Center.