Kuberanets is now available in version 1.33, the first minor release this year. Container orchestation presents 24 existing features as stable, while alpha and beta functions have increased. However, this version begins to say goodbye to some older characteristics, including endpoint API. This time theme is “Octreen: The Color of Magic,Terry Prachet’s “Scheibenwelt” is inspired by the novel series.
General available: Backofalimit, -Subresource and .Spec.succespolice
Parameter backoffLimit In Kuberanets jobs, it is considered a failure to determine the number of new efforts before the entire job. As a stable feature, the backoff limit can now be determined based on the index for indicated jobs. This means that each index can have its own backoff limit within an indicated job, which enables developers and developers to be finely classified. The failure of a specific signal does not lead to the initial failure of the entire job.
Another generally available facility is now .spec.successPolicyIt can be defined which pod indices should be successful (succeededIndexes) How many pods should be successful (succeededCount) Or combination of both. This should benefit various workloads, including simulation, which is partially completed.
Among other characteristics, there is still --subresource Reached a stable situation. It is an argument for kubactal under command like this get, patch, edit, apply Or replaceAll resources to call and update the sub -parents who support you.
New alpha and beta functions
In Kuberanets 1.14, introduced in 2019, support for direct service returns (DSR) has been passed in beta phase under Windows. This feature functions to optimize performance: Return Traffic, which is rooted by the load balancer, bypass the load billenncy by DSR and can directly respond to the client. This load reduces the load on the balancer and reduces overall delay.
Something new is SupplementalGroupsPolicy: Since Kuberanets 1.31, it has now reached the beta stage and is active by default. The purpose of the function is to ensure that the inherent group membership of container images unknowingly cannot bypass the file access authority and policy control.
New alpha features include configy tolerance HorizontalPodAutoscalersThis is to reduce scaling reactions for small metric variations. In addition, node topology labels are available using APIs at the bottom. This alpha function is to simplify the workload access node topology information.
Farewell for original closing point API
In the current Kuberanets release, some tasks are considered to be old (Padavanat) or completely eliminated. Many of these changes were already already Kuberanets on blog Taken treatment. The Kuberanets team follows some rules: among other things, it only marks a new, stable version available as well as the stable API as old. An old API continues to work until they remove, but a warning appears.
In version 1.33 it affects among other things Endpoints APIThe new endpointslis-API is available as a replacement, which is stable since Kuberanets and provides additional functions such as dual-track networking. This depression should only affect developers who use the workload or script directly endpoint API. You are encouraged to migrate to endpointslis-API.
Is completely abandoned status.nodeInfo.kubeProxyVersionThe version of this field was determined by the version-quoblets for Kube-Proxy in the nod position, but it was not consistently accurate. Already with Kuberanets 1.31 it was marked as old and has since been deactivated. In addition, host network support for Windows Pods-A feature that came into unexpected difficulties with containers and never reached a stable position. The course can be In the case way.
More information provides announcement on version 1.33 Kuberanets on blog as well as Changelog on github,
(May)
