Nicolas DUBUT

I got the same bug. When my pc reboots the k3s docker is restarted due to the docker policy but NodeHosts injection is done by k3d after the k3s docker...

Hi @iwilltry42 Thanks for your time. One more precision, My cluster was created with a 1.21 k3s image.. My second node was created with a 1.22 version ( I submitted...

Hi @iwilltry42 I didn't fill the yaml config file but the cluster was created with the correct flag to use etcd. I agree it only appears when adding a new...

Here is the relevant informations from my config.yaml used when I create the cluster ``` apiVersion: k3d.io/v1alpha4 kind: Simple metadata: name: local servers: 1 agents: 0 image: rancher/k3s:v1.21.10-k3s1 options: k3s:...

Hi @jracabado yes. It's exactly the same problem for me.

In a kubernetes environment, the full fix doesn't look good. It may be better to have a initContainer to perform this merge. I'm starting using Vouch proxy in our cluster...

if you don't fill the externalUri, it will take ingress.tls.host by default for the value (and set it in the configMap), isn't enough for your case ? I just used...

here are all my jms dependencies from the new composer.lock: "name": "jms/metadata", "version": "2.5.1", "name": "jms/serializer", "version": "3.14.0", "name": "jms/serializer-bundle", "version": "3.10.0", "name": "jms/translation-bundle", "version": "1.6.0", "name": "jms/i18n-routing-bundle", "version": "3.1.0",...

the fix is not quite good, it should be better to explain this fix: I found the reason why rancher fails to start on cgroupv2 https://github.com/rancher/rancher/issues/36238#issuecomment-1232690242 BTW maybe move the...

The most asked functionality and the simplest 😒