Kubernetes 1.16: A big step for CRDs, kubectl and Container Storage Interface

Kubernetes 1.16: A big step for CRDs, kubectl and Container Storage Interface

  • October 5, 2019
Table of Contents

Kubernetes 1.16: A big step for CRDs, kubectl and Container Storage Interface

This week Kubernetes 1.16 is expected and we want to highlight the technical features that enterprise Kubernetes users should know about. With Custom Resource Definitions (CRDs) moving into official general availability, storage improvements, and more, this release hardens the project and celebrates the main extension points for building cloud native applications on Kubernetes. 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.

Source: openshift.com

Tags :
Share :
comments powered by Disqus

Related Posts

Announcing etcd 3.4

Announcing etcd 3.4

In particular, etcd experienced performance issues with a large number of concurrent read transactions even when there is no write (e.g. “read-only range request … took too long to execute”). Previously, the storage backend commit operation on pending writes blocks incoming read transactions, even when there was no pending write. Now, the commit does not block reads which improve long-running read transaction performance.

Read More
Blog: Kubernetes 1.16: Custom Resources, Overhauled Metrics, and Volume Extensions

Blog: Kubernetes 1.16: Custom Resources, Overhauled Metrics, and Volume Extensions

Read More
OPA Gatekeeper: Policy and Governance for Kubernetes

OPA Gatekeeper: Policy and Governance for Kubernetes

The Open Policy Agent Gatekeeper project can be leveraged to help enforce policies and strengthen governance in your Kubernetes environment. In this post, we will walk through the goals, history, and current state of the project. The following recordings from the Kubecon EU 2019 sessions are a great starting place in working with Gatekeeper: If your organization has been operating Kubernetes, you probably have been looking for ways to control what end-users can do on the cluster and ways to ensure that clusters are in compliance with company policies.

Read More