Paul Krill
Editor at Large

CoreOS updates Kubernetes stack for enterprises

news
Aug 11, 20162 mins

Tectonic 1.3 features scaling, role-based access, SSO integration, and management for users, groups, and LDAP directories

shipping containers
Credit: thinkstock

Tectonic, CoreOS’s soup-to-nuts infrastructure platform for running containers, is getting upgraded with a revamped management console and improved scaling.

With Tectonic, CoreOS provides an enterprise CoreOS Linux and Kubernetes container management stack featuring a management console, SSO integration, and the Quay container registry. Tectonic 1.3, released Thursday, features an upgraded console for managing users, groups, and LDAP directories. The Tectonic look and feel has been enhanced overall, said Brandon Philips, CoreOS CTO. Increased scaling for clusters and role-based access control are featured as well.

Also enabled is support for Kubernetes 1.3. Backing for the CoreOS Rocket container engine is expected in the Tectonic 1.4 release in about six weeks.

With version 1.3, CoreOS improves installation and lifecycle management for the cluster, making Tectonic easier to deploy into bare-metal environments and upgrade afterward. “The tricky thing of bare metal is that you don’t have all those fancy APIs you might have with an OpenStack or AWS [Amazon Web Services] cloud deployment,” Philips said.

Tectonic is positioned as API-driven, cloud-native infrastructure for running containers on Kubernetes with enterprise-level security, scalability, and reliability. “The complete stack is Kubernetes all the way down to CoreOS Linux,” Philips said. “We provide and manage Kubernetes, we provide and manage the default network configuration, and then support all the way down to the actual Linux operating system. And then we bring in some necessary components like Quay for building and managing the container, and some dashboards and authentication integration.”

A Tectonic installation could cover a single datacenter or a region of AWS. Phillips said “it’s meant to manage a single zone of your application or your data center,” and a Tectonic cluster could cover, for example, five or 1,000 machines. Users have deployed Tectonic for purposes such as web applications and trading systems.

Paul Krill

Paul Krill is editor at large at InfoWorld. Paul has been covering computer technology as a news and feature reporter for more than 35 years, including 30 years at InfoWorld. He has specialized in coverage of software development tools and technologies since the 1990s, and he continues to lead InfoWorld’s news coverage of software development platforms including Java and .NET and programming languages including JavaScript, TypeScript, PHP, Python, Ruby, Rust, and Go. Long trusted as a reporter who prioritizes accuracy, integrity, and the best interests of readers, Paul is sought out by technology companies and industry organizations who want to reach InfoWorld’s audience of software developers and other information technology professionals. Paul has won a “Best Technology News Coverage” award from IDG.

More from this author