Remove support for storage class overrides

[scholzj]

Type of change

• Task

Description

This PR implements the second part of the SP-080 proposal -> it removes support for the storage overrides that allow specifying different storage classes for different nodes.

With this PR:

• For new clusters:
  • Any storage class overrides that are specified in the KafkaNodePool resources will be ignored and only rthe StorageClass configuration from the persistent volume configuration itself will be used
  • The following warnings will be added to resource conditions:

      - lastTransitionTime: "2025-01-14T14:42:47.398728342Z"
        message: In resource KafkaNodePool(myproject/aston) in API version kafka.strimzi.io/v1beta2
          the overrides property at path spec.storage.volumes.overrides has been deprecated.
          The storage overrides for individual brokers are not supported anymore since
          Strimzi 0.46.0.
        reason: DeprecatedFields
        status: "True"
        type: Warning

    as well as printed in the log:

    2025-01-14 14:46:47 WARN  StatusUtils:106 - Reconciliation #10(timer) Kafka(myproject/my-cluster): In resource KafkaNodePool(myproject/aston) in API version kafka.strimzi.io/v1beta2 the overrides property at path spec.storage.volumes.overrides has been deprecated. The storage overrides for individual brokers are not supported anymore since Strimzi 0.46.0.
    

• For existing clusters:
  • The same conditions / warnings will be used as for new clusters
  • Any existing PVCs using the storage class from the overrides will be kept and used (We do not patch the storage class or support storage class changes, so they will remain untouched by Strimzi)
  • Any new PVCs created with this configuration under Strimzi 0.46.0 or newer will ignore the overrides and use the storage class directly from the persistent storage configuraton. So e.g. when scaling up, the PVCs for the new nodes will ignore the overrides. Similarly, when the old PVCs with the storage class from the override is deleted and the operator creates a new PVC, the overrides will be ignored.

Users who want this feature should instead have different node pools that use different storage classes each.

Checklist

• Write tests
• Make sure all tests pass
• Update documentation
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
• Update CHANGELOG.md

[scholzj]

/azp run regression

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).