Platform9 Managed Kubernetes 2.4 Release Notes
Platform9 release 2.4 brings a number of major enhancements to the managed kubernetes experience.
1. Highly Available multi-master, multi-etcd Cluster Deployment
Managed Kubernetes now provides support for creating highly available and fault tolerant Kubernetes clusters that are spread across availability zones. You can specify one or more availability zones in your OpenStack or Amazon AWS environment while creating Kubernetes clusters, then Managed Kubernetes will ensure that atleast one master node is deployed within each cluster, along with configuring multi-node etcd.
2. Rolling Upgrade of Kubernetes Clusters
Managed Kubernetes now performs fully automated rolling upgrades to clusters across upgrades tomajor versions of Kubernetes. Refer to this article for more information on automated rolling upgrades to clusters.
3. 1-Click Deploy to Amazon AWS
You can auto-deploy clusters into OpenStack or Amazon AWS using 1-click deployment, as well as easily scale clusters in your cloud of choice.
Multi-tenancy is supported via integration with OpenStack Keystone. You can create one or more ‘Tenant’s and map them to namespaces on each Kubernetes clusters. Users within a tenant will only have access to the Kubernetes clusters that the Tenant has access to.
5. Upgrade to Kubernetes Version 1.4
Managed Kubernetes is now upgraded to Kubernetes version 1.4, so you can leverage all the benefits that the 1.4 release offers, including the new and improved dashboard.
- Registering of AWS cloud provider must be done per the instructions specified in this support article.
- After deploying a cluster, the Clusters list won’t show the links until you navigate away (e.g. to Nodes) and then back to Clusters. Clicking the refresh button won’t work.
- Deleted nodes are not removed from the Nodes page.
- Cleanup of AWS artifacts (instances, etc) sometimes fails.
- Keystone authorization
- (By design) Kubernetes Service Accounts not supported, except for the “default” Service Account in the “default” namespace, which has read/write privileges to all resources in the “default” namespace
- (To be fixed in next 24 hours) Requests in namespace B by an admin user of tenant A are still authorized.
- External access to apps running on cluster is not working yet. For example, won’t be able to open Guestbook sample app after it is deployed.
- For same reason, Dashboard link won’t work
- Native k8s integration with AWS features such as EBS storage and ELB is not implemented yet.