-
Notifications
You must be signed in to change notification settings - Fork 179
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
Install Scylla fails with Init:InvalidImageName
on pod/scylla-manager-manager-dc-manager-rack-0
#1617
Comments
Please attach must-gather archive - none of the info above actually shows what value is set on CRD and which one is on the pod |
Thank you for the prompt reply @tnozicka scylla-operator-must-gather-mb6gz6bj8fvj.tar.gz |
Having exactly the same issue when following the steps from https://operator.docs.scylladb.com/stable/helm.html. On the installa tion step after doing:
Getting Describe:
Doing that on WSL2 with kubernetes enabled in docker desktop. |
It's actually crazy how much steps and moving parts in there. I wonder if that could be more simple: why would we need a cert-manager to run a database(WTF?) |
@Sammers21 usually people prefer secure and encrypted traffic, especially for valuable data but that is handled internally in the operator. We don't need cert-manager per say, but something needs setup serving certificates to establish TLS for webhooks to allow kube-apiserver to validate their serving cert. @jbolila thanks, unfortunately it seems like the ScyllaCluster and its namespace is no longer there. I suspect this may be CRI runtime issue though, by looking at the scylla-operator pod.
Can you try adding this env to scylla-operator/scylla-operator deployment and do
|
Thanks @tnozicka, I have applied the env you suggested on v1.11.0, and it's working now.
|
What happened?
I'm starting with Scylla and following the instructions in:
In both cases, fails with
Init:InvalidImageName
onscylla-manager-manager-dc-manager-rack-0
The other two pods of
scylla-manager
are running:After following the instructions bellow, these two pods end in the same state:
What did you expect to happen?
Instructions provided on operator.docs.scylladb.com result in a working database.
How can we reproduce it (as minimally and precisely as possible)?
Scylla Operator version
master and v1.11.0
Kubernetes platform name and version
Platform: minikube
Minikube version: 1.32.0
Kubernetes version: 1.27.7
Scylla-operator version: master and v1.11.0
Please attach the must-gather archive.
This same issue is reported on #1441, in my test I'm using minikube and able to see the following details:
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: