# SMCP 5.10 Release Notes

**2024-05-10**

| Component              | Version          |
| ---------------------- | ---------------- |
| Airctl                 | v-5.10.0-3248001 |
| **Workload Clusters**  |                  |
| Kubernetes 1.27        | 1.27.13-pmk.150  |
| Kubernetes 1.28        | 1.28.6-pmk.69    |
| Kubernetes 1.29        | 1.29.2-pmk.42    |
| **Management cluster** |                  |
| Kubernetes 1.27        | 1.27.13-pmk.150  |

**2024-08-02:** Hotfix (updated airctl binary) released with support for RHEL 8.8

## Features/Enhancements

`Added` Added support for Ubuntu 22.04

`Added` Added support for RedHat Linux 8.8 (hotfix with updated airctl binary on 2024-08-02)

`Added` Upgraded management cluster to Kubernetes version 1.27

`Added` Added support for workload clusters with Kubernetes versions 1.28 and 1.29

## Bug Fixes

`Fixed` The problem with Pf9-vault initializing before Percona DB was up, causing sunpike and CAPI pods to enter the CrashLoopBackoff state.

## Known Issues

`Known Issue` Grafana was downgraded to v7 to address issues with Grafana v10.2 in LTS3 5.9.1. Grafana will be upgraded to v10 in SMCP 5.11

`Known Issue` AIR-1291: The `airctl upgrade-mgmt` command is broken and fails to upgrade the management cluster. This will be addressed in SMCP 5.10.1

`Known Issue` AIR-1357: On rebooting a node in the management cluster on Ubuntu OS, the nodelet service is inactive and needs to be restarted once for the management cluster to come up

`sudo systemctl enable pf9-nodeletd.service; sudo systemctl start pf9-nodeletd.service`

This will be addressed in SMCP 5.10.1 so that this workaround will not be required.

## SMCP 5.10 Kubernetes Components List

| Component                            | Kubernetes 1.29 | Kubernetes 1.28 | Kubernetes 1.27 |
| ------------------------------------ | --------------- | --------------- | --------------- |
| KUBERNETES BUILD VERSION             | 1.29.2-pmk.42   | 1.28.6-pmk.69   | 1.27.13-pmk.150 |
| CORE-DNS                             | 1.11.1          | 1.11.1          | 1.11.1          |
| CONTAINERD                           | 1.7.13          | 1.7.13          | 1.7.13          |
| RUNC                                 | 1.1.12          | 1.1.12          | 1.1.12          |
| METRICS SERVER                       | 0.6.4           | 0.6.4           | 0.6.4           |
| METAL LB                             | 0.13.11         | 0.13.11         | 0.13.11         |
| KUBERNETES DASHBOARD                 | 2.7.0           | 2.7.0           | 2.7.0           |
| CLUSTER AUTO-SCALER AWS              | 1.28.0          | 1.28.0          | 1.28.0          |
| CLUSTER AUTO-SCALER AZURE            | 1.13.8          | 1.13.8          | 1.13.8          |
| CLUSTER AUTO-SCALER CAPI             | 1.24.0          | 1.24.0          | 1.24.0          |
| FLANNEL                              | 0.24.2          | 0.24.2          | 0.22.2          |
| CALICO                               | 3.27.2          | 3.27.2          | 3.26.3          |
| ETCD                                 | 3.5.12          | 3.5.12          | 3.5.12          |
| CNI PLUGINS                          | 1.4.0           | 1.4.0           | 1.3.0           |
| KUBEVIRT                             | 1.0.0           | 1.0.0           | 1.0.0           |
| KUBEVIRT CDI                         | 1.57.0          | 1.57.0          | 1.57.0          |
| ADVANCED NETWORKING OPERATOR (LUIGI) | 0.5.4           | 0.5.4           | 0.5.4           |
| MONITORING - PROMETHEUS OPERATOR     | 0.68.1          | 0.68.1          | 0.68.1          |


---

# 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/self-managed-cloud-platform/5.12/smcp-510-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.