Feature Request: Additional Output/Logging when KubernetesSecretConfigProvider Fails to Enumerate Values

[daviddyball]

I Strimzi crew 👋 Thanks for the great tool(s)!

Backstory

I was recently pulling my hair out over a KafkaConnector not connecting to our brokers. It was complaining about not being authorised to access the subject in Schema Registry. I spent quite a bit of time debugging everything on our clusters and in Kafka, but it wasn't until I took a wild guess and hard-coded my credentials into the KafkaConnector manifest that I realised that my ${secret:<namespace>/<name>:<key>} entries in spec.config weren't being templated because we hadn't granted the correct RBAC... in reality the Connector was trying to authenticate with the following literal string in it's configuration:

value.converter.basic.auth.user.info=${secret:dev/my-app-secret:userinfo}

instead of the expected

value.converter.basic.auth.user.info=secret_username:super_secret_password

Request

It'd be really nice if there was some output indicating that the secrets weren't enumerating correctly in my spec.config. I'm not super familiar with the inner workings of the codebase, but I assume it'd be additional logging on KubernetesSecretConfigProvider and KubernetesConfigMapConfigProvider?

Thanks again for the great tool.