Use the new create db option to configure spread channel #535
Comments
|
Good timing! I am currently working on this. It will be part of the next release of the operator, which is tentatively scheduled for January 2024. |
spilchen
pushed a commit
that referenced
this issue
Oct 13, 2023
If spread encryption is selected in the CR, we now allow it for vclusterops deployments. It takes advantage of a new NMA endpoint to copy the key into the spread.conf. I included with this change the removal of a cluster restart when enabling spread encryption. This was first available in 23.3.0. This change applies to admintools deployments as well as vclusterops. Older versions of the server will continue to restart the cluster. Closes #535
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the Vertica 23.3.0-0 release a new feature is introduced which can help to configure spread channel without DB restart.
Vertica documentation about it: https://docs.vertica.com/23.3.x/en/security-and-authentication/internode-tls/control-channel-spread-tls/
Spread encryption configuration is introduced in #224 into the Operator.
It would be nice to use this new feature and configure spread encryption in create_db step and skip restart.
Could you put this on your roadmap?
The text was updated successfully, but these errors were encountered: