# PMK Release 5.16 Release Notes

## Release Summary

The Platform9 Managed Kubernetes (PMK) version 5.15 release is now generally available with active support for Kubernetes **v1.35**

## PMK 5.16.0 Release Highlights (Released 2026-04-17)

#### New Features

<mark style="color:green;">`Added`</mark> Added active support for Kubernetes **1.35**

#### Feature Updates

<mark style="color:$success;">`Updated`</mark> Updated Calico from 3.27.5 to 3.31.2.

<mark style="color:$success;">`Updated`</mark> Updated crictl to 1.33.0 and etcd to 3.5.26.

<mark style="color:$success;">`Updated`</mark> Updated Nginx within the in-cluster monitoring addon from 1.21.6 to 1.28.1.

<mark style="color:$success;">`Added`</mark> Added monitoring of MetalLB to the in-cluster monitoring helm chart.

<mark style="color:$success;">`Updated`</mark> Updated prometheus stack in the PMK addon matching the version of the in-cluster addon helm chart.

<mark style="color:orange;">`Deprecated`</mark>  The `streamingConnectionIdleTimeout` field in kubelet has been [deprecated](https://github.com/kubernetes/kubernetes/pull/131992). Containerd allows this via stream\_idle\_timeout field in `/etc/containerd/config.toml` under `[plugins."io.containerd.grpc.v1.cri"]` key. By default it will be set to “4h0m0s“,

<mark style="color:$success;">`Added`</mark> Added a new qbert API call to update the watch flag value of an addon.

#### Bug Fixes

<mark style="color:orange;">`Fixed`</mark> Resolved a UI issue where SSO Self Service User were not able to list Pods, Deployments and Services.

<mark style="color:orange;">`Fixed`</mark> Resolved an issue where the Sunpike API wasn't responding for 5 minutes after every Sunpike service restart.

<mark style="color:orange;">`Fixed`</mark> Fixed node-exporter DaemonSet pods not being created in the pf9-monitoring namespace due to Kubernetes Pod Security (baseline) enforcement on the workload cluster.

#### Deprecations, Feature Removal and EOL information

{% hint style="danger" %}
**Platform9 supports only Ubuntu 24.04 with Cilium 1.18.4.**&#x20;

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.
  {% endhint %}

{% hint style="warning" %}
RHEL 8.10 is not compatible with Kubernetes 1.35 . RHEL 8.10 by default only supports cgroup v1 which was deprecated in Kubernetes 1.35  [See the Kubernetes cgroups docs for reference.](https://kubernetes.io/docs/concepts/architecture/cgroups/?utm_source=chatgpt.com#deprecation-of-cgroup-v1)
{% endhint %}

{% hint style="danger" %}
**Kubernetes 1.32 and lower EoL**

* All clusters must be upgraded to at **least Kubernetes v1.33** before upgrading from **PMK 5.15.x to PMK 5.16**
* **Kubernetes v1.32** and lower versions are marked as *End of Life* on **PMK 5.16**
  {% endhint %}

{% hint style="warning" %}
**Kubernetes 1.33 Deprecated**

* **Kubernetes v1.33** is marked as deprecated.
* New clusters should be created on **Kubernetes v1.34** or above. However, you can continue to create new clusters on Kubernetes v1.32 or above.
  {% endhint %}

For PMK **5.16** release, check the PMK support matrix here: [Managed Kubernetes Support Matrix](/managed-kubernetes/support/support/managed-kubernetes-support-matrix.md).

#### Known Issues

<mark style="color:blue;">`Known Issue`</mark>  All links in the UI to point to still to the old documentation pages.

<mark style="color:blue;">`Known Issue`</mark> In the in-cluster monitoring addon, the Grafana dashboards report an error. Workaround is to use kubectl port-forward.

<mark style="color:blue;">`Known Issue`</mark> All existing and new AWS clusters in PMK must be configured with an `is_update`flag 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.

<mark style="color:blue;">`Known Issue`</mark> 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.

<mark style="color:blue;">`Known Issue`</mark> 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.

<mark style="color:blue;">`Known Issue`</mark> (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.

<mark style="color:blue;">`Known Issue`</mark> 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.

<mark style="color:blue;">`Known Issue`</mark> 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/kube`directory if present, even after the node is deauthorized.

<mark style="color:blue;">`Known Issue`</mark> Cluster upgrade attempt is blocked on UI post a cluster upgrade failure due to nodes being in a converging/not converged state.

<mark style="color:blue;">`Known Issue`</mark> Kubelet authorization mode is marked set to AlwaysAllow instead of Webhook.

<mark style="color:blue;">`Known Issue`</mark> 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.16.0 Latest Kubernetes Components List

<table data-header-hidden><thead><tr><th width="187">Component</th><th>Kubernetes 1.35</th><th width="187">Kubernetes 1.34</th><th>Kubernetes 1.33</th></tr></thead><tbody><tr><td>KUBERNETES BUILD VERSION</td><td>1.35.1-pmk.<strong>9</strong> <mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>1.34.2-pmk.<strong>30</strong> <mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>1.33.3-pmk.<strong>85</strong> <mark style="color:green;"><strong><code>updated</code></strong></mark></td></tr><tr><td>CONTAINERD</td><td>1.7.27</td><td>1.7.27</td><td>1.7.27</td></tr><tr><td>RUNC</td><td>1.1.12</td><td>1.1.12</td><td>1.1.12</td></tr><tr><td>CORE-DNS</td><td>1.11.1</td><td>1.11.1</td><td>1.11.1</td></tr><tr><td>METRICS SERVER</td><td>0.6.4</td><td>0.6.4</td><td>0.6.4</td></tr><tr><td>METAL LB</td><td>0.14.9</td><td>0.14.9</td><td>0.14.9</td></tr><tr><td>KUBERNETES DASHBOARD</td><td>2.7.0</td><td>2.7.0</td><td>2.7.0</td></tr><tr><td>FLANNEL CNI</td><td>0.24.2</td><td>0.24.2</td><td>0.24.2</td></tr><tr><td><strong>CALICO CNI </strong><mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>3.31.2 <mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>3.31.2 <mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>3.31.2 <mark style="color:green;"><strong><code>updated</code></strong></mark></td></tr><tr><td>CILIUM CNI</td><td>0.18.4</td><td>0.18.4</td><td>0.18.4</td></tr><tr><td>CILIUM CLI </td><td>0.18.4</td><td>0.18.4</td><td>0.18.4</td></tr><tr><td><strong>ETCD </strong><mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>3.5.<strong>26 </strong><mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>3.5.<strong>26 </strong><mark style="color:green;"><strong><code>updated</code></strong></mark></td><td>3.5.<strong>26 </strong><mark style="color:green;"><strong><code>updated</code></strong></mark></td></tr><tr><td>CNI PLUGINS</td><td>1.4.0</td><td>1.4.0</td><td>1.4.0</td></tr><tr><td>ADVANCED NETWORKING OPERATOR (LUIGI)</td><td>0.5.8</td><td>0.5.8</td><td>0.5.8</td></tr><tr><td><strong>MONITORING - PROMETHEUS OPERATOR</strong> <mark style="color:green;"><strong><code>updated</code></strong></mark></td><td><strong>0.88.12</strong></td><td><strong>0.88.12</strong></td><td><strong>0.88.12</strong></td></tr><tr><td>PROFILE AGENT</td><td>2.0.2</td><td>2.0.2</td><td>2.0.2</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.platform9.com/managed-kubernetes/overview/pmk-release-notes/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.