Lukas Grossar
Lukas Grossar
We're also seeing our clusters affected by this. I can confirm that setting `.Values.defaultRules.rules.kubeApiserver` to `false` fixes it.
/remove-lifecycle stale
Hi @dvdksn The README in `docs` at `distribution/distribution` tells me to visit `docker/docker.github.io`, which redirects me back here to `docker/docs`, so I would assume that my PR is still in...
@elmazzun In OpenShift there's probably the OpenShift monitoring operator which is in charge of maintaining the Prometheus objects, which probably revereted your change.
We'll look into that and make the cluster domain configurable in the container.
@rtprio What you're experiencing seems to be a mismatch between what peer-finder looks for (mariadb-cluster-1) and what the service reports (a59b90d7). This could be different issue related to the service.
The uuid represents the cluster uuid at the time of the crash, so it must be the same on every node in the cluster. You would need to manually edit...
Normally a Galera Cluster automatically recovers from a power loss scenario. But only if all the nodes come back up at nearly the same time, otherwise you have to find...
We're probably going to replace it with a python script, because that's easier for us to maintain. @eni might now more to that regard.
@lewismarshall For sure, PRs are always welcome. :)