Platform9 3.2 release notes
Platform9 Managed Kubernetes:
1. Introducing Application Catalog
Platform9 Managed Kubernetes introduces Application Catalog support in this release. Users can now deploy Kubernetes applications with a single click of a button. Users can add Helm repositories and associate them to Kubernetes clusters. The applications present in these repositories are exposed as applications in the catalog. Deploying an application deploys the corresponding Helm chart. You can read more about this feature here.
2. Kubernetes version upgrade to 1.7.7
In this release, Platform9 Managed Kubernetes has upgraded the Kubernetes version from 1.6.6 to 1.7.7. You can find more info on this version, along with its various features, in the Kubernetes 1.7 blog. Clusters may 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 30 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.7.7. See Install and Set Up kubectl for more information.
3. Manage Kubernetes Storage Classes
Ability to manage Kubernetes Storage Classes has been added to the Platform9 Clarity UI. From the UI, administrators can create and delete storage classes for a specific Kubernetes cluster. It is advised to create at least a default storage classes for a cluster, when a cluster is stood up. This will allow workloads that rely on Persistent Volumes, to be deployed successfully. This is also relevant in cases where applications, that are dependent on creating a Persistent Volume, are deployed from the Application Catalog. More details on this feature can be found here.
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!
Platform9 Managed Kubernetes requires certain AWS capabilities be granted to the AWS cloud providers’ account. Ensure this requirement is satisfied by the IAM policies for this user. You can find the latest IAM policy file here. Additional details can be found in the How To Create a new Amazon AWS Cloud Provider for Managed Kubernetes support article.
- An AWS private network on which an existing cluster is deployed cannot be used to deploy another Kubernetes cluster.
- 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 leu 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. Neutron performance enhancements
This release improves Neutron performance in busy environments by reducing the chattiness of neutron agents, requiring less processing when agent services are restarted/host is rebooted. It improves the reliability by adding more processing capabilities for Neutron Server and agent communication.
2. OpenStack Designate with Infoblox backend
3. Clarity UI enhancements
- All Tenants view is now available for all Openstack resources.
- Murano drag-drop application builder now provides consistent, robust user experience.
- Numerous bug fixes, UI consistency, and performance enhancements.