The open-source Kubernetes 1.4 release became generally available on October 26, bringing new security and container orchestration capabilities. On November 1, CoreOS, one of the leading contributors to Kubernetes, officially debuted its commercially supported version of Kubernetes with the Tectonic 1.4 release.
Among the key innovations that CoreOS is bringing with Tectonic 1.4 is the the concept of self-hosted clusters. With Tectonic 1.4, CoreOS is now enabling its bare-metal installer to be able to deploy self-hosted clusters. At the core of the self-hosted cluster approach is a technology called bootkube, which is a project that is currently located within the Kubernetes incubator.
"Bootkube is a helper tool for launching self-hosted Kubernetes clusters," the Bootkube Gitbhub project page explains. "When launched, bootkube will act as a temporary Kubernetes control-plane (api-server, scheduler, controller-manager), which operates long enough to bootstrap a replacement self-hosted control-plane."
From an authentication perspective, CoreOS is integrating the Dex 2.0.00alpha code to enable a Kubernetes-native approach to identity and authentication.
Also of note is integration with the Promethus monitoring project, now an official project of the Cloud Native Computing Foundation (CNCF), which is also where Kubernetes is housed.
"The Tectonic Console now displays cluster metrics collected by Prometheus right out of the box," CoreOS' release note on Tectonic 1.4 states. "Users get constant, graphical insight into CPU and RAM consumption, the number of pods on each node, network I/O, and filesystem usage."
Operators Debut to Help Manage Kubernetes Deployments
CoreOS is also looking forward to the future of Kubernetes by introducing the idea of Operators to help manage Kubernetes deployments. The basic idea behind the Operator concept is to have a tool that understands the Kubernetes API and can create, configure and manage Kubernetes instances.
"An Operator makes managing complex software on top of Kubernetes easy," Brandon Philips, CTO of CoreOS, said in a statement. "The big idea is that by installing an operator into your cluster you will get powerful new capabilities like being able to on-demand deploy new distributed databases or monitor services declaratively with simple commands."
Sean Michael Kerner is a senior editor at ServerWatch and InternetNews.com. Follow him on Twitter @TechJournalist