Skip to main content

Overview

A flaw has been detected in Kubernetes which allows privilege escalation and access to sensitive information in all Kubernetes deployments, including Tectonic. This vulnerability existed in all versions of Kubernetes since 1.2. Vulnerable versions of Tectonic Platform allow for complete exploitation of all pods running on a compute node to which a pod is scheduled with normal user privilege.

Banner

As the year comes to a close, Kubernetes contributors, our engineers included, have been hard at work to bring you the final release of 2018: Kubernetes 1.13. In recognition of the achievements the community has made this year, and the looming holiday season, we shift our focuses towards presenting this work to the world at large.

Today, we celebrate this week’s release of Kubernetes 1.12, which brings a lot of incremental feature enhancements and bug fixes across the release that help close issues encountered by enterprises adopting modern containerized systems. Each release cycle, we’re frequently asked about the theme of the release. There are always exciting enhancements to highlight, but an important theme to note is trust and stability.

Today we extend our appreciation to the teams who created Prometheus, the cloud native monitoring project, and look ahead to reflect on the future of the project.

Today we are excited to share with the community that Istio has achieved the milestone of hitting 1.0. In 2016 work began on Istio to provide an answer to the growing need for a service mesh within cloud native environments.

Three years ago the community celebrated the first production-ready release of Kubernetes, what is now a de facto standard system for container orchestration, at the 1.0 launch day at OSCON. Today we celebrate Kubernetes to not only acknowledge it on the project’s birthday but to also thank the community for the extensive work and collaboration to drive the project forward.

As we continue our work in upstream Kubernetes development to enable it for the community and enterprises alike, we’d like to celebrate the upcoming delivery of Kubernetes 1.11 expected this week.

In recent months, we've talked about our plans for Red Hat CoreOS, the new immutable, container-centric operating system bringing automated operations to Red Hat OpenShift. This week, the Fedora project announced the official launch of the Fedora CoreOS project, a new open source community effort under the Fedora banner.

We recently open sourced the Operator Framework and today we’re happy to share the next milestone: Operator Metering. Operator Metering is designed to help you gain more knowledge about the usage and costs to run and manage Kubernetes native applications (Operators). This joins the other Operator Framework components – SDK and Lifecycle Management – that are a part of the Operator Framework family, an open source toolkit designed to manage Operators in a more effective, automated, and scalable way.

In the months since CoreOS was acquired by Red Hat, we’ve been building on our vision of helping companies achieve greater operational efficiency through automation. Today at Red Hat Summit we’ve outlined our roadmap for how we plan to integrate the projects and technologies started at CoreOS with Red Hat’s, bringing software automation expertise to customers and the community.

Subscribe to CoreOS Blog