Kubernetes Compatibility

This topic describes the compatibility for versions of Redpanda, Redpanda Operator, and the Helm charts. The tables identify the version requirements and compatibility guidelines.

Redpanda Self-Managed version numbers follow the convention AB.C.D, where AB is the two digit year, C is the feature release, and D is the patch release. For example, v22.3.1 indicates the first patch release on the third feature release of the year 2022. Patch releases include bug fixes and minor improvements, with no change to user-facing behavior. New and enhanced features are documented with each feature release. You can find a list of all releases on GitHub.

Versioning scheme and compatibility policy

The Redpanda Helm chart and Redpanda Operator are versioned and tested alongside specific Redpanda core releases, Kubernetes, and Helm.

Starting from version v25.1.1-beta1, the Redpanda Operator and Redpanda Helm chart follow a new versioning scheme aligned with Redpanda core releases:

  • v25.1 refers to the Redpanda core feature release deployed by default.

  • The patch version denotes the patch version for either the operator or Helm chart. It is not the patch version of Redpanda core.

  • The beta version is used for pre-release versions of the Redpanda Operator and Helm chart. These versions are not intended for production use.

Each Redpanda Operator and Helm chart version supports the corresponding Redpanda core version plus one minor version above and one below. This approach ensures flexibility during upgrades. For example, Redpanda Operator version 25.1.1 supports Redpanda core versions 25.2.x, 25.1.x, and 24.3.x.

Redpanda Operator and Helm chart versions are supported only while their associated Redpanda core version remains supported. If the core version reaches end of life (EoL), the corresponding versions of the Redpanda Operator and Helm chart also reach EoL.

Beta versions are available only for testing and feedback. They are not supported by Redpanda and should not be used in production environments. To give feedback on beta releases, reach out to the Redpanda team in Redpanda Community Slack.

Kubernetes version policy

The minimum supported Kubernetes version is 1.27.0-0.

The Kubernetes versions listed in the compatibility matrix are suggested ranges, based on testing and reported usage. Not every patch or minor version within these ranges is explicitly tested.

To request compatibility testing of a Kubernetes version outside of the given ranges, contact Redpanda support.

Redpanda Core has no direct dependency on Kubernetes. Compatibility is influenced indirectly by the Helm chart or Operator that you use.

Compatibility matrix

Redpanda Core / rpk Helm Chart Operator Helm Chart Operator Helm CLI Kubernetes

25.1.x

25.1.1-beta1, 5.10.x, 5.9.x

25.1.1-beta1, 0.4.41, 0.4.36

25.1.1-beta1, 2.4.x, 2.3.x

3.12+

1.28.x - 1.32.x[1]

24.3.x

25.1-k8s-beta, 5.9.x

25.1-k8s-beta, 0.4.41, 0.4.36, 0.4.29

25.1-k8s-beta, 2.4.x, 2.3.x, 2.2.x

3.11+

1.28.x - 1.31.x[1]

24.2.x

5.9.x, 5.8.x

0.4.29

2.2.x

3.10+

1.27.x - 1.30.x[1]

By default, the Redpanda Helm chart depends on cert-manager for enabling TLS. Make sure to install a version of the cert-manager CRDs that supports the certificates.cert-manager.io/v1 resource. See the cert-manager release notes.

Redpanda Console integration

Redpanda Console is deployed through the Redpanda Helm chart. It is included as a subchart, and its version is determined by the version of the parent Helm chart.

The Redpanda Helm chart defines which Redpanda Console versions it supports. When you install or update the Helm chart, it automatically selects the appropriate Redpanda Console version.

Upgrading the Helm chart may also upgrade Redpanda Console. Because of this built-in dependency, selecting a different Helm chart version can change the Redpanda Console version deployed in your environment.

Redpanda Console Helm Chart Operator

v3.x.x

v25.1.1-beta1

v25.1.1-beta1

v2.x.x

5.10.1, 5.9.x, 5.8.x

2.4.x, 2.3.x, 2.2.x

Next steps

1. These Kubernetes versions are suggested ranges, based on testing and reported usage. Not every patch or minor version within these ranges is explicitly tested.