Extensibility is the goal

Kubernetes 1.14 arrives with tons of new features and major updates

Eirini-Eleni Papadopoulou
© Shutterstock / Evannovostro  

The first Kubernetes release for 2019 is here! Version 1.14 offers a huge list of new features including major Kubectl updates, Persistent Local Volumes going GA, and much more. Let’s take a look.

Kubernetes’ first release for 2019 brings a lot of goodies!

With 10 features moving to stable, 12 in beta, and 7 brand new, Kubernetes 1.14 is the release with the most enhancements that graduated to stable.

Let’s have a closer look at some of the most interesting highlights of this release.

Extensibility is the goal

Production-level support for Windows nodes – Kubernetes now officially supports adding Windows nodes as worker nodes and scheduling Windows containers, enabling a vast ecosystem of Windows applications to leverage the power of our platform. Here are some of the key features of enabling Windows containers in Kubernetes include:

  • Support for Windows Server 2019 for worker nodes and containers
  • Support for out of tree networking with Azure-CNI, OVN-Kubernetes, and Flannel
  • Improved support for pods, service types, workload controllers, and metrics/quotas to closely match the capabilities offered for Linux containers

Kubectl updates – There are several notable updates for Kubectl including:

  • New Kubectl docs and logo: The documentation for kubectl has been rewritten from the ground up with a focus on managing Resources using declarative Resource Config.
  • Kustomize integration: The declarative Resource Config authoring capabilities of kustomize are now available in kubectl through the -k flag (e.g. for commands like apply, get) and the kustomize subcommand.
  • Kubectl plugin mechanism graduating to stable: Allows developers to publish their own custom kubectl subcommands in the form of standalone binaries.

Persistent local volumes GA – Makes locally attached storage available as a persistent volume source.

PID limiting is moving to beta – Administrators are able to provide pod-to-pod PID isolation by defaulting the number of PIDs per pod as a beta feature. In addition, administrators can enable node-to-pod PID isolation as an alpha feature by reserving a number of allocatable PIDs to user pods via node allocatable.

There are also some more notable updates we should mention:

  • Pod priority and preemption
  • Pod Readiness Gates
  • Harden the default RBAC discovery clusterrolebindings

Head over to the official changelog for the extensive list of new features and updates.

SEE ALSO: Multiple stages within a Kubernetes cluster

Getting started

If you can’t wait to get started with the new version of Kubernetes, you can find it available for download on GitHub but you can also install 1.14 using kubeadm.

Eirini-Eleni Papadopoulou
Eirini-Eleni Papadopoulou was the editor for Coming from an academic background in East Asian Studies, she decided that it was time to go back to her high-school hobby that was computer science and she dived into the development world. Other hobbies include esports and League of Legends, although she never managed to escape elo hell (yet), and she is a guest writer/analyst for competitive LoL at TGH.

Inline Feedbacks
View all comments