Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

PMK Release 5.17 Release Notes

Discover the latest enhancements in Platform9 Managed Kubernetes (PMK) version 5.17. This release supports Kubernetes v1.36.

Release Summary

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

PMK 5.17.0 Release Highlights (Released 2026-08-25)

New Features

Added Added active support for Kubernetes 1.36

Feature Updates

Updated Updated Etcd from 3.5.26 to 3.6.13.

Bug Fixes

Fixed Security vulnerabilities:

  1. CVE-2025-68121: crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption.

  2. CVE-2026-33186: gRPC-Go has an authorization bypass via missing leading slash in :path.

  3. CVE-2020-14343: Improper Input Validation in PyYAML.

Fixed int32 to int64 format for myASN and peerASN of BGPPeer metallb.

Deprecations, Feature Removal and EOL information

Platform9 supports only Ubuntu 24.04 with Cilium 1.18.4.

The following OS and kernel combinations are not compatible with Cilium 1.18:

  • Ubuntu 22.04 LTS GA kernel (5.15.0-67-generic). Upgrade to Ubuntu 24.04 which provides 5.15.0-1090-kvm to ensure Cilium 1.18.4 compatibility.

  • RHEL 8.10 with kernel 4.18.0-553.el8_10.x86_64.

RHEL 8.10 is not compatible with Kubernetes 1.36 . RHEL 8.10 by default only supports cgroup v1 which was deprecated in Kubernetes 1.35 See the Kubernetes cgroups docs for reference.

Kubernetes 1.33 and lower EoL

  • All clusters must be upgraded to at least Kubernetes v1.34 before upgrading from PMK 5.16.x to PMK 5.17

  • Kubernetes v1.33 and lower versions are marked as End of Life on PMK 5.17

Kubernetes 1.34 Deprecated

  • Kubernetes v1.34 is marked as deprecated.

  • New clusters should be created on Kubernetes v1.35 or above. However, you can continue to create new clusters on Kubernetes v1.34 or above.

For PMK 5.17 release, check the PMK support matrix here: Managed Kubernetes Support Matrix.

Known Issues

Known Limitation ImageVolume (new in K8s 1.36, mounts an OCI image as a pod volume) conformance test — unsupported by bundled containerd 1.7.27; needs containerd 2.x

Known Issue All links in the UI to point to still to the old documentation pages.

Known Issue In the in-cluster monitoring addon, the Grafana dashboards report an error. Workaround is to use kubectl port-forward.

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 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.17.0 Latest Kubernetes Components List

KUBERNETES BUILD VERSION

1.36.2-pmk.18 updated

1.35.1-pmk.10 updated

1.34.2-pmk.31 updated

CONTAINERD

1.7.27

1.7.27

1.7.27

RUNC

1.1.12

1.1.12

1.1.12

CORE-DNS

1.11.1

1.11.1

1.11.1

METRICS SERVER

0.6.4

0.6.4

0.6.4

METAL LB

0.14.9

0.14.9

0.14.9

KUBERNETES DASHBOARD

2.7.0

2.7.0

2.7.0

FLANNEL CNI

0.24.2

0.24.2

0.24.2

CALICO CNI

3.31.2

3.31.2

3.31.2

CILIUM CNI

0.18.4

0.18.4

0.18.4

CILIUM CLI

0.18.4

0.18.4

0.18.4

ETCD updated

3.6.13 updated

3.6.13 updated

3.6.13 updated

CNI PLUGINS

1.4.0

1.4.0

1.4.0

ADVANCED NETWORKING OPERATOR (LUIGI)

0.5.8

0.5.8

0.5.8

MONITORING - PROMETHEUS OPERATOR

0.88.12

0.88.12

0.88.12

PROFILE AGENT

2.0.2

2.0.2

2.0.2

PreviousPMK Release Notes
NextPMK Upcoming Releases

Last updated

Was this helpful?