Skip to content
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

K8SSAND-1880 ⁃ Do not mount encryption-cred-storage #442

Closed
burmanm opened this issue Nov 9, 2022 · 1 comment · Fixed by #443
Closed

K8SSAND-1880 ⁃ Do not mount encryption-cred-storage #442

burmanm opened this issue Nov 9, 2022 · 1 comment · Fixed by #443
Assignees
Labels
enhancement New feature or request ready-for-review Issues in the state 'ready-for-review'

Comments

@burmanm
Copy link
Contributor

burmanm commented Nov 9, 2022

What is missing?
The encryption-cred-storage is an old way to create internode encryption CAs. We don't usually need that and there's better ways to do it with cert-manager, yet we always add these mounts and create the CAs.

We should improve the situation and only create the mount if needed (if that certain hardcoded path is used or existing cluster has it) to the StatefulSet.

Why do we need it?
This also helps in the migration process.

Environment

  • Cass Operator version:

    Insert image tag or Git SHA here

Anything else we need to know?:

┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: K8SSAND-1880
┆Priority: Medium
┆Link To Issue: https://k8ssandra.atlassian.net/browse/K8SSAND-1880

@burmanm burmanm added the enhancement New feature or request label Nov 9, 2022
@sync-by-unito sync-by-unito bot changed the title Do not mount encryption-cred-storage K8SSAND-1880 ⁃ Do not mount encryption-cred-storage Nov 9, 2022
@jsanda
Copy link
Contributor

jsanda commented Nov 10, 2022

there's better ways to do it with cert-manager

Am I correct in thinking that cass-operator will not do this and it will instead be up to the user?

@adejanovski adejanovski moved this to Ready For Review in K8ssandra Nov 16, 2022
@adejanovski adejanovski added the ready-for-review Issues in the state 'ready-for-review' label Nov 16, 2022
@burmanm burmanm removed the status in K8ssandra Nov 17, 2022
@burmanm burmanm moved this to Ready For Review in K8ssandra Nov 17, 2022
Repository owner moved this from Ready For Review to Done in K8ssandra Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready-for-review Issues in the state 'ready-for-review'
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants