Christiaan Goossens

@KlavsKlavsen Kubernetes will never destroy pod 0 of a statefulset if you asked for one or more pods. It's ordered. Removing the readyness probe does not solve this issue, it...

> I tried to kill the 0 pod, but the new pod fails the same way - so something else seems to also be an issue. I think your issue...

Hi all, this is issue possibly still exists, but I have moved on to the CloudnativePG operator instead. Its easier to restore in my opinion too and has less components...

I am also a bit stuck on this, especially with the kube-vip CCM, https://kube-vip.io/docs/usage/cloud-provider/ If I have a dual stack cluster, and a CIDR for IPv4 and one for IPv6...

Is there any way to implement this ourselves with the flows right now?

> Yes, change login duration on default-authentication-login stage Amazing, thanks!

@robotdjman Did you also change the Dockerfiles to include all the code and commands? Would love to run this with only the images from the repository and a mounting dir...

@matskiv What would be the best way to put a liveness probe on the vcluster container in your opinion? In some cases the 6443 TCP connection or even HTTPS might...

For k0s the `/run/k0s/status.sock` socket or `k0s status` command might be options, although I am not sure if that actually indicates a working cluster. What does the `syncer` do to...

Tried it with my statefulset, this seems to work: ``` livenessProbe: exec: command: - kubectl - get - --raw=/livez failureThreshold: 10 initialDelaySeconds: 60 periodSeconds: 2 successThreshold: 1 timeoutSeconds: 1 readinessProbe:...