Open hongbo-miao opened 1 month ago
Hmm I found env
SCHEMA_REGISTRY_KAFKASTORE_SECURITY_PROTOCOL
SCHEMA_REGISTRY_KAFKASTORE_SASL_MECHANISM
SCHEMA_REGISTRY_KAFKASTORE_SASL_JAAS_CONFIG
SCHEMA_REGISTRY_KAFKASTORE_SASL_CLIENT_CALLBACK_HANDLER_CLASS
do not exist in https://github.com/bitnami/containers/tree/main/bitnami/schema-registry#configuration
It is for confluentinc/cp-schema-registry.
I opened a feature request at https://github.com/bitnami/containers/issues/70769. I guess container needs to support it first.
Thanks so much for this feature request, given changes in the image are required before supporting this in the chart I'll mark this issue as "on-hold".
Name and Version
bitnami/schema-registry 21.0.0
What is the problem this feature will solve?
I am hoping to mount
aws-msk-iam-auth-2.2.0-all.jar
file and use AWS IAM auth way according toHere is my current Helm values.yaml:
If I use
it will throw error:
However, in this case, I do not need
externalKafka.sasl
, I triedand
but none of them helps me bypass InvalidArgument check.
What is the feature you are proposing to solve the problem?
It would be great to support
AWS_MSK_IAM
way.What alternatives have you considered?
Use old
SASL_SSL
way.