We’re pleased to announce the delivery of Kubernetes 1.15, our second release of 2019! Kubernetes 1.15 consists of 25 enhancements: 2 moving to stable, 13 in beta, and 10 in alpha. The main themes of this release are:
Project sustainability is not just about features. Many SIGs have been working on improving test coverage, ensuring the basics stay reliable, and stability of the core feature set and working on maturing existing features and cleaning up the backlog.
The community has been asking for continuing support of extensibility, so this cycle features more work around CRDs and API Machinery. Most of the enhancements in this cycle were from SIG API Machinery and related areas.
We have pretty exciting news this week as Red Hat is announcing the General Availability of their Apache Kafka Kubernetes operator. Red Hat AMQ Streams delivers the mechanisms for managing Apache Kafka on top of OpenShift, our enterprise distribution for Kubernetes.
Redis Labs is integrating its enterprise platform as a hosted and managed database service on Red Hat’s OpenShift Container Platform. That integration includes built-in support for Red Hat’s recently launched Kubernetes Operator.
The Redis Enterprise integration will allow customers to deploy and manage Redis databases as a stateful Kubernetes service. It will also allow users to run Redis Enterprise on-premises or across any cloud environment.
We are pleased to announce that F5 Networks, Nutanix, Tencent Cloud and Helm providers are now available for HashiCorp Terraform. This blog will detail the new providers and include links to additional resources.
Amazon Elastic Container Service for Kubernetes (EKS) now supports dynamic admission controllers, allowing customers to deploy custom webhooks that enable additional open source tools for controlling network traffic and monitoring Kubernetes clusters on AWS.
Admissions controllers are a Kubernetes construct that allow you to run a piece of code after an API request has been authenticated and authorized, but before an object's state within the Kubernetes cluster is stored. Dynamic admission controllers allow you to accept, reject, or alter admission requests.
Enables tools like Istio
The AWS Service Operator is an open source project in an alpha state which allows to you manage your AWS resources directly from Kubernetes using the standard Kubernetes CLI, kubectl. It does so by modeling AWS Services as Custom Resource Definitions (CRDs) in Kubernetes and applying those definitions to your cluster. This means that a developer can model their entire application architecture from container to ingress to AWS services, backing it from a single YAML manifest. We anticipate that the AWS Service Operator will help reduce the time it takes to create new applications, and assist in keeping applications in the desired state.
At the start of 2018, Unbabel’s DevOps team set out to solve these rising issues. Our goal was to make deploys faster and easier for developers, reduce the time it takes to scale a project’s resources up or down, and automate as much as possible any extra configurations for logging, application metrics, and resource control. Ideally, even make them invisible to the projects themselves. After some investigation, Kubernetes seemed to offer what we were after
This release continues to focus on internal improvements and graduating features to stable in Kubernetes. This newest version graduates key features such as security and Azure. Notable additions in this release include two highly-anticipated features graduating to general availability: Kubelet TLS Bootstrap and Support for Azure Virtual Machine Scale Sets (VMSS).