Pierre Ozoux
Pierre Ozoux
@kurzdev do you want to PR this small change? I mean in the Dockerfile, not the compose.
Thanks a lot @kurzdev :)
@CorneliousJD Did you follow this discussion? https://github.com/nextcloud/docker/issues/1414 I think the community of people using this docker image is in favor of this change. I also tried to change the warning...
@flypenguin you again? :P I'm also following silently this issue, and I also think that having another mean of auth like oauth, OIDC or SAML would make it easier for...
I'm also looking to have this fixed (with promtail >= 2.5.0): https://github.com/grafana/loki/commit/8a914b5c2fab45f250a9adc83d32aafcdeebbd30 I try a PR :)
In the mean time, I added that to my values.yml of the loki-stach chart: ``` promtail: image: tag: 2.5.0 ``` So far so good :+1:
duplicate of https://github.com/xetys/hetzner-kube/issues/13
Also, we'll need an upgrade command (for k8s and underlying OS). Once we have this command, this issue would be solved somehow. The only remaining question is should we perform...
Yes, noticed that too. I think what is happening is that wireguard is created, then kubeadm is configured to use wireguard IPs, and then when flannel starts, it discovers interface...
Yeah, maybe you have to clean some folders too, and iterfaces. I've used this command when I used kubeadm, to reset node: ``` systemctl stop kubelet systemctl stop docker rm...