What’s new in Kubernetes 1.22

Victoria D. Doty

By generating containerized apps radically a lot easier to take care of at scale, Kubernetes has develop into a key element of the container revolution. Here’s the latest.

Kubernetes 1.22, produced August five, 2022, is made up of the subsequent new and updated options:

  • Server-side Use is now normally obtainable. This previously beta-only attribute makes it possible for objects on Kubernetes servers to be developed and modified declaratively, by having the developer explain their intent. Improvements to an item are tracked on a subject-by-subject foundation, so that any attempts to alter a subject modified and “owned” by another person else will be rejected. Server-side Use is intended at some point to exchange the primary kubectl use operate simply because it provides a less difficult system for controllers to make alterations to their configurations.
  • External credential companies, obtainable by way of plug-ins, are now out of beta.
  • Etcd, the default back again-conclusion storage for Kubernetes has been updated to a new launch (three.five.) with bug fixes and new options all around log management.
  • QoS for memory resources is obtainable as a beta attribute. The cgroups v2 API can now be utilized to designate how memory is allotted and isolated for pods, generating it a lot easier to deploy a number of apps that could possibly fight every single other for memory utilization.
  • Improved assistance for acquiring and running on Microsoft Home windows. Some Kubernetes options for Home windows are nevertheless alpha—e.g., privileged containers—but it is now achievable to run much more of the early-assistance Kubernetes options on Home windows by manually developing the Home windows kubelet and kube-proxy binaries.

Other alterations in Kubernetes 1.22:

  • Nodes can now run on programs wherever swap memory is activated if wanted. Kubernetes admins utilized to have to disable swap area ahead of placing up Kubernetes. (Alpha attribute.)
  • Aid for default, cluster-extensive seccomp profiles is now obtainable. (Alpha.)
  • kubeadm can now be run as non-root if wanted, by running the control aircraft with lower privileges. (Alpha.) All other Kubernetes node factors can be run experimentally as a non-root consumer as well.
  • Some APIs have been deprecated and adjusted, in distinct the API for Ephemeral Containers (which was an alpha attribute to begin with and did not have a stable API).

Kubernetes 1.20, produced in December 2020, launched these major alterations:

  • The Docker runtime is getting deprecated. Nevertheless, this does not mean Docker pictures or Dockerfiles really do not operate in Kubernetes any more. It just implies Kubernetes will now use its possess Container Runtime Interface (CRI) merchandise to execute containers as an alternative of the Docker runtime. For most customers this will have no substantial impact—e.g., any current Docker pictures will operate good. But some difficulties could possibly end result when dealing with runtime useful resource boundaries, logging configurations, or how GPUs and other exclusive hardware interact with the runtime (a little something to be aware for those people employing Kubernetes for machine mastering). The preceding connection provides aspects on how to migrate workloads, if wanted, and what difficulties to be aware of.
  • Quantity snapshot operations are now stable. This makes it possible for quantity snapshots—images of the state of a storage volume—to be utilized in production. Kubernetes apps that count on hugely specific state, these as pictures of database information, will be a lot easier to develop and manage with this attribute active.
  • Kubectl Debug is now in beta, making it possible for popular debug workflows to be executed from inside the kubectl command-line surroundings. 
  • API Precedence and Fairness (APF) is now enabled by default, even though nevertheless in beta. Incoming requests to kube-apiserver can be sorted by priority amounts, so that the administrator can specify which requests should be pleased most quickly.
  • Process PID Limiting is now in normal availability. This attribute ensures that pods are not able to exhaust the selection of approach IDs obtainable on a Linux host, or interfere with other pods by employing up much too many procedures.

Kubernetes 1.seventeen, produced in December 2019, launched the subsequent key new options and revisions: 

  • Quantity snapshots, launched in alpha in Kubernetes 1.12, are now promoted to beta. This attribute makes it possible for a quantity in a cluster to be snapshotted at a presented second in time. Snapshots can be utilized to provision a new quantity with facts from the snapshot, or to roll back again an current quantity to an before snapshotted edition. Quantity snapshots make it achievable to accomplish elaborate facts-versioned or code-versioning operations inside of a cluster that weren’t previously achievable.
  • Far more of the “in-tree” (included by default) storage plug-ins are now getting moved to the Container Storage Interface (CSI) infrastructure. This implies less direct dependencies on those people motorists for the core edition of Kubernetes. Nevertheless, a cluster has to be explicitly updated to assistance migrating the in-tree storage plug-ins, but a profitable migration should not have any unwell outcomes for a cluster.
  • The cloud company labels attribute, at first launched in beta back again in Kubernetes 1.2, is now normally obtainable. Nodes and volumes are labeled primarily based on the cloud company wherever the Kubernetes cluster runs, as a way to explain to the relaxation of Kubernetes how those people nodes and volumes should be taken care of (e.g., by the scheduler). If you are employing the before beta versions of the labels you, you should update them to their new counterparts to avoid complications.

Exactly where to down load Kubernetes

You can down load the Kubernetes supply code from the releases site of its formal GitHub repository. Kubernetes is also obtainable by way of the update approach delivered by the numerous distributors that source Kubernetes distributions.

What is new in Kubernetes 1.sixteen

Kubernetes 1.sixteen, produced in September 2019, is made up of the subsequent new and revised options:

  • Tailor made useful resource definitions (CRDs), the very long-advisable system for extending Kubernetes operation launched in Kubernetes 1.7, are now officially a normally obtainable attribute. CRDs have previously been extensively utilized by 3rd get-togethers. With the move to GA, many optional-but-advisable behaviors are now essential by default to maintain the APIs stable.
  • Numerous alterations have been built to how volumes are taken care of. Main between them is transferring the quantity resizing API, found in the Container Storage Interface (CSI), to beta.
  • Kubeadm now has alpha assistance for becoming a member of Home windows worker nodes to an current cluster. The very long-expression target in this article is to make Home windows and Linux nodes both of those initial-course citizens in a cluster, as an alternative of having only a partial established of behaviors for Home windows.
  • CSI plug-in assistance is now obtainable in alpha for Home windows nodes, so those people programs can get started employing the similar range of storage plug-ins as Linux nodes.
  • A new attribute, Endpoint Slices, makes it possible for for bigger scaling of clusters and much more overall flexibility in dealing with network addresses. Endpoint Slices are now obtainable as an alpha take a look at attribute.
  • The way metrics are taken care of proceeds a major overhaul with Kubernetes 1.sixteen. Some metrics are getting renamed or deprecated to provide them much more in line with Prometheus. The system is to take out all deprecated metrics by Kubernetes 1.seventeen.
  • Finally, Kubernetes 1.16 removes a selection of deprecated API versions. 

What is new in Kubernetes 1.fifteen

Kubernetes 1.fifteen, produced in late June 2019, provides the subsequent new options and advancements:

  • Far more options (now in alpha and beta) for Tailor made Source Definitions, or CRDs. CRDs in Kubernetes are the foundation of its extensibility technological innovation, making it possible for Kubernetes situations to be tailored with no slipping out of conformance with upstream Kubernetes expectations. The new options contain the capability to transform CRDs involving versions (a little something very long obtainable for indigenous resources), OpenAPI publishing for CRDs, default values for fields in OpenAPI-validated schemas for CRDs, and much more.
  • Native significant availability (HA) in Kubernetes is now in beta. Placing up a cluster for HA nevertheless involves arranging and forethought, but the very long-expression target is to make HA achievable with no any 3rd-bash application.
  • Far more plug-ins that take care of volumes have been migrated to use the Container Storage Interface (CSI), a constant way to take care of storage for hosted containers. Among the new options launched in alpha for CSI are quantity cloning, so that new persistent volumes can be primarily based on an current 1.

Other alterations in Kubernetes 1.fifteen contain:

  • Certification management now instantly rotates certificates ahead of expiration.
  • A new framework for plug-ins that accomplish scheduling operations has entered alpha.

What is new in Kubernetes 1.14

Version 1.14 of Kubernetes, produced in March 2019, is made up of the subsequent alterations:

  • Microsoft Home windows Server 2019 is now officially supported as a system for running both of those Kubernetes worker nodes and container scheduling. This implies full Kubernetes clusters can run on Home windows solely, relatively than having a blend of Home windows and Linux programs.
  • The plugin system for Kubectl, the default Kubernetes command-line instrument, is now a stable attribute, allowing builders apply their possess Kubectl subcommands as standalone binaries.
  • Persistent neighborhood volumes are now a stable attribute. This lets locally attached storage be utilized by Kubernetes for persistent volumes. Apart from offering much better general performance than employing network-attached storage, it also can make it a lot easier (and probably less costly) to stand up a cluster.
  • Process ID limiting for Linux hosts is now a beta attribute. This stops any 1 pod from employing up much too many approach IDs and consequently triggering useful resource exhaustion on the host.

What is new in Kubernetes 1.thirteen

Version 1.thirteen of Kubernetes was produced in December 2018, with the subsequent new and upgraded options:

  • Kubeadm, a instrument developed to make it a lot easier to established up a Kubernetes cluster, is finally obtainable as a thoroughly supported attribute. It walks an admin through the basic principles of placing up nodes for production, becoming a member of them to the cluster, and applying finest techniques alongside the way. It also provides a way for infrastructure-orchestration equipment (Puppet, Chef, Salt, and many others.) to automate cluster setup.

  • The Container Storage Interface, or CSI, is now also obtainable as a supported attribute. CSI makes it possible for extensions for Kubernetes’s quantity layer, so that storage plugins can operate with Kubernetes with no having to be built element of Kubernetes’s core code.

  • Kubernetes now makes use of CoreDNS as its default DNS server. CoreDNS will work as a drop-in alternative for other DNS servers, but was constructed to integrate with Kubernetes by way of plug-ins and integration with Kubernetes options these as Prometheus monitoring metrics.

What is new in Kubernetes 1.12

Released in late September 2018, Kubernetes 1.12 provides to normal availability the Kubelet TLS Bootstrap. The Kubelet TLS Bootstrap makes it possible for a Kubelet, or the principal agent that runs on each Kubernetes node, to be a part of a TLS-secured cluster instantly, by requesting a TLS consumer certificate through an API. By automating this approach, Kubernetes makes it possible for clusters to be configured with larger security by default.

Also new in Kubernetes 1.12 is assistance for Microsoft Azure’s digital machine scale sets (VMSS), a way to established up a team of VMs that instantly ramp up or down on schedule or to fulfill desire. Kubernetes’s cluster-autoscaling attribute now will work with VMSS.

Other new options in Kubernetes 1.12:

  • Snapshot and restore operation for volumes (alpha).
  • Tailor made metrics for pod autoscaling (beta). This makes it possible for personalized position disorders or other metrics to be utilized when scaling a pod—for occasion, if resources that are specific to a presented deployment of Kubernetes need to be tracked as element of the application’s management strategy.
  • Vertical pod scaling (beta), which makes it possible for a pod’s useful resource boundaries to be various throughout its lifetime, as a way to much better take care of pods that have a significant price linked with disposing of them. This is a very long-standing item on many would like lists for Kubernetes, simply because it makes it possible for for strategies to deal with pods whose behaviors are not simple to take care of under the current scheduling strategy.

What is new in Kubernetes 1.eleven

Released in early July 2018, Kubernetes 1.eleven adds IPVS, or IP Digital Server, to provides significant-general performance cluster load balancing employing an in-kernel technological innovation which is less complicated than the iptables procedure ordinarily utilized for these items. Sooner or later, Kubernetes will use IPVS as the default load balancer, but for now it is opt-in.

Tailor made useful resource definitions, billed as a way to make personalized configuration alterations to Kubernetes with no breaking its standardizations, may perhaps now be versioned to enable for sleek transitions from 1 established of personalized resources to a further around time. Also new are approaches to outline “status” and “scale” subresources, which can integrate with monitoring and significant-availability frameworks in a cluster.

Other major alterations contain:

Next Post

How to work with Azure Queue Storage in C#

A queue is a details composition that functions on a FIFO (first in first out) basis. Items are inserted at the rear of the queue and eliminated from the front. The term “Enqueue” denotes the operation that inserts details in the queue, whilst the term “Dequeue” denotes the removing of […]

Subscribe US Now