Jorge
Jorge
the problem persists with 1.6.6
I am not 100% sure but I will try to create a secret with this content and try username: whatever password: whatever
Ok, thats the workround. There is another problem related with TLS. How can I use argo events exotic feature and the "verify" certificates option in nats Is there any way...
``` apiVersion: v1 data: client-auth: kind: Secret metadata: name: whatever type: Opaque ``` The base64 encoded string is basically username: whatever password: whatever My eventbus ``` apiVersion: argoproj.io/v1alpha1 kind: EventBus...
same for a stream `kubectl logs nack-XXXXXXX` `Nothing done for stream "XXXX" (prevent-delete=false, prevent-update=false)` I have to delete the object and recreate it
same problem in kube-adm deployed cluster with flatcar stable. the file is there in all nodes but no reboots. it is a vanilla installation of kured in kubernetes v1.27.2 time="2023-08-11T10:01:27Z"...
in my case, finally the reboot started without changing anything. I do not know the reason. If I find something I will tell you
A new flatcar release and the same problem. The /var/run/reboot-required file exists but no reboots. I am working with the 1.14.0 release and i do not find a way to...
Nope @ckotzbauer I do not see that log I only see the same as in my Aug 11 annotation
updates with 1.15.0 . no changes inside a kured pod in a node with /var/run/reboot-required present /tmp # /usr/bin/nsenter -m/proc/1/ns/mnt -- test -f /var/run/reboot-required /tmp # echo $? 0 /tmp...