Authenticate node communications#944
Conversation
…nces Signed-off-by: Chance Zibolski <[email protected]>
- Add cluster secret to clusters configuration - Support supplying username/password in host configuration - Support supplying internode communication password via k8s secret - Sets the password in the env-vars of the pod, and configures the password to source it from the env-var. - Update TLS test to configure authentication between nodes Signed-off-by: Chance Zibolski <[email protected]>
9abd234 to
b57e6fc
Compare
|
Hi @chancez , we are making some changes for inter-cluster communication in scope of 0.19 release now. This PR should go after we are done with those changes. Also, I think it makes sense to move user/password for inter-cluster communication at cluster level. It is not a part of hostTemplate. |
1 similar comment
|
Hi @chancez , we are making some changes for inter-cluster communication in scope of 0.19 release now. This PR should go after we are done with those changes. Also, I think it makes sense to move user/password for inter-cluster communication at cluster level. It is not a part of hostTemplate. |
|
@alex-zaitsev sure, that seems reasonable. So next to the |
|
If we move it from the host configuration, how is this supposed to be configured for the auto-generated clusters? https://github.com/Altinity/clickhouse-operator/blob/master/pkg/model/ch_config_generator.go#L336-L398 |
|
@alex-zaitsev Thoughts on how to deal with configuring auto generated clusters when internode authentication is configured? |
|
@sunsingerus , there are two distinct changes here:
I think <secret> should be default if it passes all tests |
|
@chancez , we will implement the following: |
|
@alex-zaitsev Sounds good. I can rebase and I think this PR is pretty close to the configuration you've suggested, so hopefully this can be merged soon then. |
|
@alex-zaitsev I'm looking back into this but my question from earlier is still unanswered:
Setting |
|
@chancez , secrets for inter-cluster communication are implemented in 0.20.0. See usage examples: |
Please check items PR complies to:
next-releasebranch, not intomasterbranch1. More infoThis is based on #938 , because I wanted to put it up for review, but didn't feel like it was necessary for it to be part of the existing PR. Let me know if you think they should be combined.