Product reviews, deals and the latest tech news

The 1.26 version of Kubernetes boosts security and storage while hinting at dynamic resource allocation

Where cloud-native apps are concerned, one technology stands head and shoulders above the rest: Kubernetes.

Open-source container orchestration system Kubernetes was created by Google in 2014. The Cloud Native Computing Foundation (CNCF), an offshoot of the Linux Foundation that has been responsible for Kubernetes development since2015, has the backing of thousands of engineers and hundreds of supporting companies.

Kubernetes is supported by every major public cloud in 2022, including Google Kubernetes Engine (GKE), Amazon Elastic Kubernetes Service (EKS), and Microsoft Azure’s Managed Kubernetes Service (AKS) (EKS).

Multiple vendor distributions, such as OpenShift from Red Hat, Canonical Kubernetes, and the SUSE Rancher Kubernetes Engine, all provide support for Kubernetes (RKE). The open-source project that is being upgraded today to version 1.26 serves as the upstream source for all the work done by cloud and software suppliers.

The latest Kubernetes 1.26 version includes improved speed, security, storage, and a container registry. The release is the result of the combined efforts of 6,877 people from 976 enterprises.

No one piece of code can take credit for the vast majority of the enhancements made in the 1.26 release; rather, it is the overall organisation of the project that has been praised. The Kubernetes Enhancement Proposals process is used to create any new capabilities and upgrades (KEPs). All suggested improvements for a specific version were recorded in a basic spreadsheet up to the 1.26 release. A brand new project improvement dashboard has been added to the latest edition in order to better monitor the progress of features.

Kubernetes 1.26 release lead Leonard Pahlke told VentureBeat, “Previously we had a spreadsheet for tracking, which was bad, it had a lot of custom improvements to it and it was broken most of the time.” Now that we have the new system in place, everything works so much better.

In the latest release of Kubernetes, version 1.26, security is front and centre.

The security of the new 1.26 version is one of the major upgrades

For more information on how to implement this security feature, see KEP-3031, which is updated in version 1.26 and makes digitally signing code easier. Increased code authenticity and confidence may be established by digital signature, which is essential for the implementation of a secure Software Bill of Materials (SBOMs). SBOMs are a crucial part of the software supply chain for both free and paid applications.

Chainguard, an IT services company, supports the open-source sigstore effort that Kubernetes use as its cosign technology..

Software engineer and technical lead for the Kubernetes SIG release at Chainguard, Adolfo Garca Veytia, recently spoke with VentureBeat and announced that the company had moved the Kubernetes Enhancement Proposal (KEP) [3031] into beta, signifying the completion of all planned work to be signed with sigstore.

When this KEP is finished, not just the container images but all programme artefacts will be signed. In addition, I can’t stress enough how important this achievement is and how much better off Kubernetes developers will be in terms of security.

In addition to these fixes, version 1.26 also introduces support for Windows privileged containers with KEP-1981, a long-awaited security improvement that has been in the works for over two years. Kubernetes works on both Linux and Windows, albeit there are some differences in the features available on each platform. When compared to a standard container, a privileged container may access more resources on a Kubernetes host. Until recently, Kubernetes only worked with containers running on Linux.

Allocation of resources will be dynamic soon

In KEP-3063, we keep tabs on an early version of a feature that will allow for more agile allocation of available resources in the latest 1.26 upgrade.

Kubernetes originally gained popularity as a means to run workloads in the public cloud, but it has since been implemented on-premises and in edge computing settings, where the benefits of dynamic resource allocation will be most apparent.

In order to make connecting GPUs and other resources easier, “Dynamic resource allocation effectively offers a new interface with a new API,” as Pahlke put it. This opens the door to new applications for edge computing.

Now that version 1.26 is out, attention will shift to the next upgrade. The next major upgrade to Kubernetes is scheduled around the end of April 2023. There are normally three Kubernetes releases each year.