We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
HCD used /etc/cassandra mount instead of /opt/hcd/resources/cassandra/conf. This prevents running in readOnlyRootFilesystem after the HCD fixes.
1.22.1
1.30
No response
┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: CASS-65
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
HCD used /etc/cassandra mount instead of /opt/hcd/resources/cassandra/conf. This prevents running in readOnlyRootFilesystem after the HCD fixes.
What did you expect to happen?
How can we reproduce it (as minimally and precisely as possible)?
cass-operator version
1.22.1
Kubernetes version
1.30
Method of installation
No response
Anything else we need to know?
No response
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-65
The text was updated successfully, but these errors were encountered: