PMK Release 5.14 Release Notes

Release Summary

The Platform9 Managed Kubernetes (PMK) version 5.14 release is now generally available with active support for Kubernetes v1.33

PMK 5.14.0 Release Highlights (Released 2025-08-25)

New Features

Added Added active support for Kubernetes 1.33

Feature Updates

Added Improvements to Cilium CNI

Added Updated libraries/ module dependencies to fix CVEs

Deprecations, Feature Removal and EOL information

• There are no Operating Systems deprecations in PMK 5.14 release. Check the PMK support matrix here: Managed Kubernetes Support Matrix

Bug Fixes

Fixed Removed the -cloud-provider flag for API server to support k8s 1.33 for AWS clusters

Known Issues

Known Issue All existing and new AWS clusters in PMK must be configured with an is_updateflag and restricted security group rules. Without this cluster updates (such as AMI updated) and upgrades may fail. Please reach out to Platform9 support for this configuration.

Known Issue During PMK cluster upgrades, pf9-kube package uninstallation may be incomplete if workload containers are not stopped and removed. Please reach out to Platform9 support if this occurs.

Known Issue On Rocky Linux 9 (tested on 9.2 and 9.4), Platform9's pf9-kube package installs iptables-services as a dependency. With recent updates to the upstream repositories, installation will fail due to a missing dependency on iptables-legacy-* packages.

Known Issue (On Rocky Linux 9) Users will need to install the legacy packages by running dnf install iptables or dnf install iptables-utils on workload cluster nodes. Since this is a recent upstream change, a solution will be provided in upcoming releases by packaging the required packages along with pf9-kube package.

Known Issue AWS clusters using flannel CNI need to be updated to use port 2379 instead of 4001 from1.22 version onwards. Workaround is to go to the "Edit cluster" option on the UI and clicked on "Update cluster" without making any changes. This adds the 2379 ingress rule to the master ELB.

Known Issue When a detach operation is performed on a master node in a multi master cluster, it takes approximately 30 minutes to complete all the detach operations and perform cleanup on the node. Therefore, if you want to reattach this node to any other cluster, you need to wait for the nodelet to stop all the phases and perform cleanup before attempting to reattach the node.

Known Issue In some scenarios, after a node is removed from the qbert clusters, nodelet fails to cleanup the data. Workaround is to check and remove the /var/opt/pf9/kubedirectory if present, even after the node is deauthorized.

Known Issue Cluster upgrade attempt is blocked on UI post a cluster upgrade failure due to nodes being in a converging/not converged state.

Known Issue Kubelet authorization mode is marked set to AlwaysAllow instead of Webhook.

Known Issue PMK Cloud provider created directly in Sunpike cannot be used to create qbert clusters. Qbert cloud providers will work to create both qbert and sunpike clusters. But cloud providers created directly in sunpike CANNOT be used to create qbert clusters. Please use the appropriate one based on your needs.

Package Updates

PMK 5.14 Latest Kubernetes Components List