Kubernetes 1.15 Offers More Scalability Against Custom Resource Definitions

The Kubernetes container architecture is now available in version 1.15. The second version of the current year presents a total of 25 innovations – only two of which are clbadified as stable, the rest still in the beta or alpha stage. Stable additions include two new commands for the Kubectl command line interface: get and to describe should facilitate the construction of third-party API extensions and custom resource definitions (CRDs). Kubernetes developers should also benefit from the now stable support of Go modules.

The CLI designed to execute commands for Kubernetes clusters had already been completely redesigned in the latest version of Kubernetes 1.14. The newly added Kubectl commands are just one of many additional preparatory steps for the general availability of custom resource definitions and Admission Webhooks, which the Kubernetes team looks forward to for one of the next versions of the container orchestration.

New structural validation scheme for CRDs

The OpenAPI validation scheme in CRDs must be transferred in the medium term to the concept of structural schema, which is basically the complete non-polymorphic and complete typification of each field in a domain. Custom Resources provides. The revised OpenAPI publication for CRDs in Kubernetes 1.15 is intended for the structural schema – but it is not yet mandatory.

However, structural validation is a prerequisite for the new pruning feature of CRD, also available in beta. It allows the automatic deletion of unknown fields in objects sent to the Kubernetes API and aims to improve data consistency and security. The pruning installs in the CRD with the order spec.preserveUnknownFields: false Activate. In addition, users have two new beta features around Webhooks. These include, on the one hand, the ability to convert "on the fly" between different versions, as native resource users are accustomed to, and, on the other hand, reminder enhancements.

As part of efforts to further simplify the installation, upgrade, and configuration of Kubernetes, kubeadm has also been improved. Thus, among other things, high availability (HA) is available as a beta function. Users can use well-known kubeadm commands initialization and join configure and deploy a high availability control plan. Certificate management should now work more efficiently. Finally, kubeadm has its own logo.

You will find a complete overview of all the improvements of the new version of Kubernetes in the official blog post of this publication. If you want to try Kubernetes, you will find the version of the container's orchestration on GitHub.

(Map)