Platform9 3.5 release notes
Platform9 Managed Kubernetes
1. Kubernetes version upgrade to 1.9.6
This version of Platform9 Managed Kubernetes has upgraded the Kubernetes version from 1.8.x to 1.9.6. You can find more info on this version, along with its various features, in the blog for Kubernetes 1.9 release. Clusters can be upgraded to this Kubernetes version by using the “Upgrade Cluster” button in the Clusters view of the Infrastructure page of the Platform9 Clarity UI. We highly recommend users upgrade their clusters at the earliest convenience and within 15 days of the release of new Platform9 Managed Kubernetes versions. Users may need to obtain a compatible kubectl for this version if their existing kubectl is not compatible with Kubernetes 1.9.6. See Install and Set Up kubectl for more information.
2. Upgrade of Kubernetes dependent components
In this version, two key components needed for Kubernetes have been upgraded.
- Docker will be upgraded from v1.12.6 to v17.09.1. This version has many enhancements and stability fixes from Docker.
- We have moved etcd software from v2.2.5 to v2.3.7. This sets us up to move to the new v3 version of the etcd software in a subsequent release. Look out for an announcement in a future release about moving to a newer version of etcd.
3. Clarity UI improvements
Certain screens in the Clarity UI for Platform9 Managed Kubernetes would take a long time to load. We have made many enhancements to make this UI experience better and faster.
4. Bug fixes and product improvements
This release also contains a number of performance optimizations and bug-fixes that should result in a better user experience for your Platform9 cloud platform! Some significant ones are listed below
- We have fixed our Kubernetes deployments to be compatible with the recommended Horizontal Pod Autoscaling feature in Kubernetes.
- During cluster creation in AWS, pre-flight checks would create a test instance in AWS to validate user provided configuration. There was a bug that prevented cleanup of such instances in rare occasions. This bug has been fixed in this release.
- On upgrading a cluster, the upgrade operation may timeout. An unfortunate bug in our previous release did not clean up some containers created by our monitoring infrastructure. Depending on the number of containers to be cleaned up, the upgrade operation may take much longer than expected leading to a timeout.
- AWS VPC’s subnets that are created as of cluster creation by Platform9 Managed Kubernetes cannot be shared between Kubernetes clusters.
- There are limitations when using AWS Route 53 private hosted zones with your AWS clusters:
- Private hosted zones are supported only when deploying into an existing VPC that has been associated with the hosted zone. Before using a private hosted zone, create a VPC and associate it with the hosted zone.
- Because the hosted zone is private, the API and Service FQDNs can only be resolved from within the associated VPC.
- Moving to leverage CNI for networking, one important issue is CNI’s lack of support for hostPort. Application deployments are expected to use NodePort and other service types in lieu of hostPort unless absolutely necessary (using hostNetwork becomes a must for applications needing to expose hostPorts). For more information see Kubernetes best practices.
Platform9 Managed OpenStack
1. Cinder project upgraded to Pike release
This version of Cinder also updates the recommended API version to v3. Platform9 UI has been updated to take advantage of new Cinder version. The new version of Cinder has been tested against LVM, NFS and SolidFire storage backends. If you use a proprietary storage backend for Cinder, please let us know.
2. Scale enhancements
Platform9 now takes advantage of a horizontally scaled architecture to provide improved performance. Performance fixes improve responsiveness of Clarity UI.
3. HA bugfixes
- Fixed a bug which disabled HA function after first failure
- Improved resiliency of workflow to enable HA feature
- Fixed a bug with on-host service (pf9-ha-slave). It now properly starts on host reboot