Platform9 Managed Kubernetes: An Overview

Enterprise infrastructure environments can benefit from Platform9’s SaaS-managed Kubernetes services that enable onboarding in minutes (typically 30 minutes), provide ongoing operational monitoring with committed 24/7/365 SLAs, troubleshooting and orchestration of Kubernetes upgrades.

Platform9’s infrastructure-agnostic Managed Kubernetes service works across all public clouds and on-premise infrastructure environments: bare metal, enterprise Linux, KVM, VMware vSphere, OpenStack. Organizations can reduce costs and increase operational flexibility by seamlessly running applications anywhere. The Clarity UI allows users to easily manage multiple Kubernetes clusters, different cloud providers, and multiple private data centers. In addition, managing multi-tenancy using Kubernetes namespaces and the selected SSO provider, and viewing and management of services, pods, and deployments are all simplified.

Platform9’s Managed Kubernetes creates highly available, multi-master, multi-etcd Kubernetes clusters that can span across availability zones in both the private or public cloud environment. With this capability, users can tolerate local failures across one or more availability zones.

With no interdependence among systems with Platform9’s managed Kubernetes, software can be decoupled from the underlying infrastructure stack. Users can leverage policy controls for scaling and versioning software deployment.

New Features in Platform9 Managed Kubernetes v3.3

In v3.3, Platform9 has come out with two salient features that we think are very critical from an enterprise-readiness perspective:

On-Premise Infrastructure Support

Enabling managed Kubernetes services for orchestration of containers deployed on-premise infrastructure (bare metal servers or virtualized infrastructure) is increasingly becoming critical for many mid-to-large size enterprises.

Platform9 v3.3 has significantly solidified on-premise support for managed Kubernetes. A prominent feature of this release is an OpenStack cloud provider that makes it easy to integrate with an OpenStack, VMware or Linux KVM environment. Currently Linux KVM support is in beta, but VMware support will be generally available as part of version 3.3 of managed Kubernetes.

Role-Based Access Control (RBAC) Support for Kubernetes

Another important new feature of v3.3 is Role-Based Access Control (RBAC) support for Kubernetes. Starting with release 1.8, RBAC became generally available for Kubernetes. Platform9, as part of our 3.3 release of managed Kubernetes, includes an upgrade to the 1.8 version of Kubernetes so that we can deliver Kubernetes in its generally available form.

As part of this new managed Kubernetes platform, we are enabling a new user role with the addition of self-service user support. Now, in addition to administrator users, this new self-service user support allows enterprises to carve out the Kubernetes environment and allocate different roles to different parts of the organization.

Now, some users can be administrator users while others can be self-service users, who do not necessarily have complete access to all of your Kubernetes infrastructure. However, self-service users can have the access and ability to deploy workloads on Kubernetes clusters, depending on the RBAC policies that have been set for them by their administrators.

v3.3 Is the Enterprise-Ready Kubernetes Solution

These new features ― on-premise infrastructure support and RBAC support with the new self-service user ― provide a very strong native enterprise-ready Kubernetes experience for your on-premise infrastructure. You can contact us to learn more about the 3.3 version of Platform9 managed Kubernetes – and stay tuned for more updates from Platform9.

If you’re ready to try Kubernetes in your enterprise, try out the Platform9 sandbox or start a free trial.

Madhura Maskasky
Madhura Maskasky is Co-founder and VP Product at Platform9.

The browser you are using is outdated. For the best experience please download or update your browser to one of the following: