Kubernetes 1.15 arrives with structural schemas and kubeadm updates

The second Kubernetes release for 2019 is here!

Kubernetes 1.15 has continuous improvement and extensibility as its main themes and it brings a nice list of improvements.

This release includes a total of 25 enhancements including two features moving to stable and 13 in beta.

Let’s have a look at the most interesting highlights.

All the highlights

Structural schema – From 1.15 on each schema gets checked against the restriction called “structural schema”. This restriction enforces non-polymorphic and complete typing of each field in a CustomResource. In the future, structural schemas will be required for all new features including:

• beta: CustomResourceDefinition Webhook Conversion
• beta: CustomResourceDefinition OpenAPI Publishing
• beta: CustomResourceDefinitions Pruning
• alpha: CustomResourceDefinition Defaulting
• beta: Admission Webhook Reinvocation & Improvements

kubeadm – Features and stability work continue to be pushed to the cluster lifecycle building block, including:

• High availability (HA) capability promoted to beta, allowing users to use the familiar kubeadm init and kubeadm join commands.
• Certificate management has become more robust with kubeadm now seamlessly rotating all your certificates (on upgrades) before they expire.
• The kubeadm configuration file API is moving from v1beta1 to v1beta2

SIG Storage – Introduces new alpha functionality in CSI that doesn’t exist in the Kubernetes Storage subsystem yet, like volume cloning which enables users to specify another PVC as a “DataSource” when provisioning a new volume.

SEE ALSO: Automated build and deployment of Docker containerized OSGi applications on Kubernetes

Other notable updates include:

• Support for go modules in Kubernetes Core
• Continued preparation on cloud provider extraction and code organization. The cloud provider code has been moved to kubernetes/legacy-cloud-providers for easier removal later and external consumption.
• Kubectl ‘get and describe’ now works with extensions
• Nodes now support third party monitoring plugins.
• A new Scheduling Framework for schedule plugins is now Alpha
• ExecutionHook API designed to trigger hook commands in the containers for different use cases is now Alpha.
• Continued deprecation of extensions/v1beta1, apps/v1beta1, and apps/v1beta2 APIs; these extensions will be retired in 1.16

You can check out the official release notes for all the detailed information.