Michael Burman

Something in your deployment has caused the cass-operator to lose its access to the imageConfig. There should be a ConfigMap which has suffix ``-manager-config`` (the prefix can change depending on...

I assume this is the same as https://github.com/k8ssandra/cass-operator/issues/130 ?

Chart.Name should always be available in Helm (and it is defined in our Chart.yaml). How did you install it without Chart.Name existing?

Are you using k8ssandra-operator as a subchart in another Helm chart? That said, the error description: "Error: no chart name found" comes from Helm itself and indicates something else than...

That's the approach we use in our own projects that use k8ssandra-operator as subchart. There's a plan to modify the CRD maintenance at some point so we'll probably tackle this...

> Only via user intervention to install the Prometheus operator. Given how critical monitoring is, it is important that users are notified that things aren't working so that they can...

> Kustomize has explicitly dealt with this and applies manifests in the order in which they are referenced in the kustomize.yaml. What you're talking about is whether operations are commutative,...

> Lastly, I am now of the opinion that we should remove the k8sContexts checks in the webhook and consider how to handle that differently. Maybe a combo of events...

> owever on the other hand, we do not actually verify that the ClientConfigs are real in sense of what's stored in the Kubernetes but how k8ssandra-operator sees them Similar...

Ready itself is set to true when initial startup has finished, or waking up from Stopped. It's not changed if some other operation is doing something else, but this method...