You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the apiCurio CR, there is an ability to configure the storage as kafkasql/streams
where you can manage to set the authentication in two ways:
tls
scram
in the scram, there is a field called truststoreSecretName, which according to the documentation is a required field
and inaction, not setting this variable at all, will cause the operator not to generate other scram-related ENV variables in the registry deployment.
while in fact this field is supposed to be Optional, as when using Signed Certificates for Kafka listeners, there is no need to configure any truststore certs on the client-side, as those certificates are trusted by default
I am interested in a patch that can allow me not to set this variable, while the operator still creates other scram auth related env variables for the deployment resource
The text was updated successfully, but these errors were encountered:
in the apiCurio CR, there is an ability to configure the storage as kafkasql/streams
where you can manage to set the authentication in two ways:
in the scram, there is a field called truststoreSecretName, which according to the documentation is a required field
and inaction, not setting this variable at all, will cause the operator not to generate other scram-related ENV variables in the registry deployment.
while in fact this field is supposed to be Optional, as when using Signed Certificates for Kafka listeners, there is no need to configure any truststore certs on the client-side, as those certificates are trusted by default
I am interested in a patch that can allow me not to set this variable, while the operator still creates other scram auth related env variables for the deployment resource
The text was updated successfully, but these errors were encountered: