-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for ssl consumer properties using values #28
Comments
If CMAK supports passing SSL params to its consumer - I can add this to this project, To be clear, are you talking about securing consumer traffic with SSL ? |
According to this issue SSL settings are the same for the all clusters managed by single CMAK instance. So, I'd advice you to just install several instances of CMAK operator, one for each cluster \ SSL key. |
well that's the point i made in the initial comment. the old kafka-manager chart did support it and the issue you referenced is exactly the reason i think this was removed but i do need it as my current pattern is to create multiple kafka clusters with 1 certificate created for cmak and allowed in all clusters. so if i PR this feature you have no objection to it? |
yes |
Sorry, I still don't understand what do you trying to achieve :( |
yes that is what i want |
currently the chart as far as i can tell does not support it |
Seems I had understood now. There is no possibility of passing customer properties file into CMAK |
yes we will need to add 2 components here. 1 will be a configMap to replace the consumer.properties ate /cmak/conf in the ui container of the deployment. the other component will need to be a secret which will add a truststore and a keystore into the ui container... |
Makes sense @oferzi23 |
already on it PR will be pushed soon... |
@oferzi23 released 1.6.0 with your changes, could you please confirm that everything is working fine ? |
Hello @oferzi23 |
ii is my understanding that due to the limitations of cmak, which specifies that 1 consumer properties object will apply to all clusters effectively requiring allowing the same certificate across all managed clusters, is not the best solution. i do need this in my implementation.
so the question is, can we add this support here and allow passing consumer properties to the chart using it's values. if this is accepted i will add the support on my open fork and open the respective PR. WDYT?
The text was updated successfully, but these errors were encountered: