-
Notifications
You must be signed in to change notification settings - Fork 66
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
Unable to use cassandra 4.1.X version #717
Comments
cert-manager simply mounts the crt files to the disk (through secret), that's perfectly normal. It seems you have some issues in your Kubernetes environment as even the operator can't reliably connect to it. Perhaps overload? |
But when I kept other conditions unchanged, it ran fine when using version 4.0.1 of Cassandra. |
None of those logs have any indication that it would have even noticed your CassandraDatacenter. That's all startup logs of the operator, not the actual processing instructions. So the operator doesn't know if you deployed 4.1, 4.0.1 or nothing at all at that stage. So if something succeeded later with 4.0.1, that means the operator had already started correctly. Then it would have done the same for 4.1 |
But this is the log generated by the Cassandra pod, not the log generated by the operator. |
I saw that in 4.1, the self-developed k8ssandra-client was used. Is this related to this? |
I tried again and again and got the same error message. |
That log: |
What happened?
This is the log that appears in Cassandra:
It looks for the /tmp/k8s-webhook-server/serving-certs/tls.crt certificate file locally
You can view this document: https://book.kubebuilder.io/cronjob-tutorial/running.html
But now I don't understand that even though I have started cert-manager, it still looks for the certificate file locally? What is the logic here?
What did you expect to happen?
No response
How can we reproduce it (as minimally and precisely as possible)?
Deploy and install Cassandra 4.1.X version and it will appear.
cass-operator version
v1.21.0
Kubernetes version
v1.28.2
Method of installation
helm
Anything else we need to know?
No response
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-72
The text was updated successfully, but these errors were encountered: