Language Selection

English French German Italian Portuguese Spanish

Kubernetes 1.16 available from Canonical

Filed under

Canonical announces full enterprise support for Kubernetes 1.16, with support covering Charmed Kubernetes, MicroK8s and kubeadm.

MicroK8s will be updated with Kubernetes 1.16 enabling users access to the latest upstream release with a single-line command in under 60 seconds. In addition, MicroK8s gets new add-ons with one line installs of Helm and Cilium as well as enhancements, upgrades and bug fixes. Cilium adds enhanced networking features including Kubernetes Network Policy support. With MicroK8s 1.16, users can develop and deploy enterprise grade Kubernetes on any Linux desktop, server or VM across 42 Linux distros.

Canonical’s Charmed Kubernetes 1.16 will come with exciting changes like support for Kata Containers, AWS IAM, SSL passthrough and more. Using Kata Containers, insecure or untrusted pods can be run safely in isolation without disrupting trusted pods in deployments. Identity Access Management on AWS can be used to login to your Charmed Kubernetes cluster. Users get more control over their deployments while benefitting from reduced complexity due to improved LXD support and enhanced Prometheus and OpenStack integration.

“At Canonical, we enable enterprises by reducing the complexity of their Kubernetes deployments. We are actively involved in the Kubernetes community to ensure we listen to, and support our users’ and partners’ needs. Staying on top of security flaws, community issues and features to improve Kubernetes is critical to us. We keep the Ubuntu ecosystem updated with the latest Kubernetes, as soon as it becomes available upstream,” commented Ammar Naqvi, Product Manager at Canonical.

Read more

A Look into the Technical Details of Kubernetes 1.16

  • A Look into the Technical Details of Kubernetes 1.16

    Custom Resource Definitions (CRDs) were introduced into upstream Kubernetes by Red Hat engineers in version 1.7. From the beginning, they were designed as a future-proof implementation of what was previously prototyped as ThirdPartyResources. The road of CRDs has focused on the original goal of making custom resources production ready, bringing it to be a generally available feature in Kubernetes, highlighted with the promotion of the API to v1 in 1.16.

    CRDs have become a cornerstone of API extensions in the Kubernetes ecosystem, and is the basis of innovation and a core building block of OpenShift 4. Red Hat has continued pushing CRDs forward ever since, as one of the main drivers in the community behind the features and stability improvements, which finally lead to the v1 API. This progress made OpenShift 4 possible.

    Let’s take a deeper look at what will change in the v1 API of Custom Resource Definitions (in the API group). The main theme is around consistency of data stored in CustomResources:

Custom Resources, Overhauled Metrics, and Volume Extensions

More from Red Hat

  • Hello Kubernetes 1.16: Custom Resource Definitions ease the creation and long term management of APIs

    Kubernetes 1.16 is expected to arrive this week, and with it comes a host of new changes that help ease management for users of this container orchestration platform. For users of Kubernetes, and of Red Hat OpenShift, this release signals the arrival of the general availability for Custom Resource Definitions (CRDs).

    When building open source software, duties and tasks must be distributed among large numbers of contributors, some of whom may even be in direct competition with one another. While this may sound like a risky, Machiavellian scenario, in practice, there’s far less rivalry. Instead, the whole project becomes a collaborative board game with individual high scores.

    Those high scores ebb and flow as teams take charge of features, lead them to completion and exchange leadership roles over the course of the development of the project. We say all that to say this: Kubernetes 1.16 saw a great deal of work and guidance across the ecosystem, as well as from Red Hat and Google (top upstream corporate contributors). All vendors and the community at large can benefit from the updates made in this release, especially with the prime time for CRDs, which are a main extension point for building cloud native applications on Kubernetes.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Type Title Author Replies Last Postsort icon
Story today's leftovers Roy Schestowitz 06/03/2021 - 9:15am
Story today's howtos Roy Schestowitz 06/03/2021 - 9:10am
Story Security Incidents and Microsoft/Proprietary Role Roy Schestowitz 06/03/2021 - 9:07am
Story Android Leftovers Rianne Schestowitz 06/03/2021 - 8:49am
Story This week in KDE: Adaptive panel opacity and auto-restored unsaved documents in Kate! Rianne Schestowitz 06/03/2021 - 8:34am
Story Kubuntu Focus M2 Linux laptop now available with NVIDIA RTX 30x series graphics Rianne Schestowitz 06/03/2021 - 8:29am
Story Canonical/Ubuntu Deal With ADLINK Roy Schestowitz 3 06/03/2021 - 7:44am
Story Self-supported Red Hat Enterprise Linux Server virty users see stealth inflation Roy Schestowitz 06/03/2021 - 3:27am
Story Christian Hergert: A GTK 4 based Text Editor Roy Schestowitz 06/03/2021 - 3:16am
Story Linux 5.12-rc2 Roy Schestowitz 06/03/2021 - 3:14am