Redpanda supports decreasing core count in v24.3

CHANGELOG.md

@@ -11,6 +11,7 @@
 ### [5.9.14](https://github.com/redpanda-data/helm-charts/releases/tag/redpanda-5.9.14) - 2024-11-28
 #### Added
 #### Changed
+* note to indicate Core count decreasing will be possible starting from 24.3 Redpanda version
 #### Fixed
 * Fixed the description of `-memory` and `--reserve-memory` in docs.
 #### Removed

charts/redpanda/README.md

@@ -637,7 +637,7 @@ CPU resources. For details, see the [Pod resources documentation](https://docs.r
 
 ### [resources.cpu.cores](https://artifacthub.io/packages/helm/redpanda-data/redpanda?modal=values&path=resources.cpu.cores)
 
-Redpanda makes use of a thread per core model. For details, see this [blog](https://redpanda.com/blog/tpc-buffers). For this reason, Redpanda should only be given full cores.  Note: You can increase cores, but decreasing cores is not currently supported. See the [GitHub issue](https://github.com/redpanda-data/redpanda/issues/350).  This setting is equivalent to `--smp`, `resources.requests.cpu`, and `resources.limits.cpu`. For production, use `4` or greater.  To maximize efficiency, use the `static` CPU manager policy by specifying an even integer for CPU resource requests and limits. This policy gives the Pods running Redpanda brokers access to exclusive CPUs on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#static-policy.
+Redpanda makes use of a thread per core model. For details, see this [blog](https://redpanda.com/blog/tpc-buffers). For this reason, Redpanda should only be given full cores.  Note: You can increase cores, but decreasing cores is supported only from 24.3 Redpanda version.  This setting is equivalent to `--smp`, `resources.requests.cpu`, and `resources.limits.cpu`. For production, use `4` or greater.  To maximize efficiency, use the `static` CPU manager policy by specifying an even integer for CPU resource requests and limits. This policy gives the Pods running Redpanda brokers access to exclusive CPUs on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#static-policy.
 
 **Default:** `1`
 

charts/redpanda/values.yaml

@@ -365,8 +365,8 @@ resources:
     # For details, see this [blog](https://redpanda.com/blog/tpc-buffers).
     # For this reason, Redpanda should only be given full cores.
     #
-    # Note: You can increase cores, but decreasing cores is not currently supported.
-    # See the [GitHub issue](https://github.com/redpanda-data/redpanda/issues/350).
+    # Note: You can increase cores, but decreasing cores is supported only from
+    # 24.3 Redpanda version.
     #
     # This setting is equivalent to `--smp`, `resources.requests.cpu`, and `resources.limits.cpu`.
     # For production, use `4` or greater.