For our combined kraft setup, We recently migrated the kafka broker and controller authentication mechanisms as follows: Broker: from sasl.mechanism.inter.broker.protocol="PLAIN" to "SCRAM-SHA-512" Controller: from SASL_SSL to SSL. After applying these changes, we restarted the Kafka pods in Kubernetes. However, once the pods came up, the brokers were unable to authenticate with each other. When we deleted the Kafka PVC and restarted the pods, they ran successfully — suggesting that the old inter-broker credentials were still being persisted in the PVC.
Is this an expected behaviour? or are we missing something while implementing new auth mechanism
