Cluster out-of-sync after modifying storage sizes

Solution Unverified - Updated -

Issue

  • Replication Steps
  1. We attempted to resize (increase) PVC on Kafka, Zookeeper - Applied to cluster
  2. OCP platform we are using does not support automatic resizing of PVC
  3. Cluster Administrator modified persistent backend storage to meet requirements of new size
  • What happened: resources out of sync thus preventing changes on our kafka cluster

    • PVC is not getting resized on kubernetes (expected)
    • Strimzi Kafka resource definition of the PV is resized
    • Thus PVC and Kafka resource not matching, resulting in us not being able to apply resource changes to the cluster
  • What we are expecting:

    • Clarity on the issue of out of sync and why it is getting out of sync
    • Instructions on how to rollback the changes to get the clusters in-sync

Environment

  • Red Hat AMQ Streams
    • 1.3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content