Yesterday, the team at Kubernetes released Kubernetes 1.14, a new update to the popular open-source container orchestration system. Kubernetes 1.14 comes with support for Windows nodes, kubectl plugin mechanism, Kustomize integration, and much more.
This had more stable enhancements than any prior Kubernetes release
Everyone wrote a KEP
We released on time, with .deb's and .rpm's available immediately
And soon there will be a t-shirt that is three wolf moon but the wolves are cats and the moon is Kubernetes
— Aaron Crickenberger (@spiffxp) March 25, 2019
What’s new in Kubernetes 1.14?
Support for Windows Nodes
This release comes with added support for Windows nodes as worker nodes. Kubernetes now schedules Windows containers and enables a vast ecosystem of Windows applications. With this release, enterprises with investments can easily manage their workloads and operational efficiencies across their deployments, regardless of the operating systems.
With this release, the declarative resource config authoring capabilities of kustomize are now available in kubectl through the -k flag. Kustomize helps the users in authoring and reusing resource config using Kubernetes native concepts.
kubectl plugin mechanism
This release comes with kubectl plugin mechanism that allows developers to publish their own custom kubectl subcommands in the form of standalone binaries.
Administrators can now provide pod-to-pod PID (Process IDs) isolation by defaulting the number of PIDs per pod. Pod priority and preemption in this release enables Kubernetes scheduler to schedule important pods first and remove the less important pods to create room for more important ones.
Users are generally happy and excited about this release.
#kubernetes 1.14 is out! 🥳 A huge thanks to the release team! 🙏🙏🙏 It is amazing how a community so big and articulated can coordinate and be so disciplined on the common objective
— Fabrizio Pandini (@fabriziopandini) March 25, 2019
A user commented on HackerNews, “The inclusion of Kustomize into kubectl is a big step forward for the K8s ecosystem as it provides a native solution for application configuration. Once you really grok the pattern of using overlays and patches, it starts to feel like a pattern that you’ll want to use everywhere”
To know more about this release in detail, check out Kubernetes’ official announcement.