Markus Reiter

The health check is still reporting as failed on this node: ``` NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT talos-cp-1 apid Running OK 13m28s ago Health check successful talos-cp-1...

Okay, I did that, here is the `dmesg` output: ``` talos-cp-1: kern: notice: [2022-06-30T12:55:07.922370274Z]: Linux version 5.15.48-talos (@buildkitsandbox) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Jun...

I manually removed the node from `etcd` and reset the node again (with `--graceful=true`, this time). After applying the config again it rejoined correctly this time.

@mrwulf, thanks, I do also have a workaround using `grep`/`awk`. To be clear, I am talking about the `Server` version, not the `Client`. The `Client` version is already kept up-to-date...

> did you first deploy with flannel and then switched to cilium? Yes, I switched from Flannel to Cilium.

Yes, I did that, every pod has been restarted.

Any update on this? I also just encountered this, also with k3OS on Proxmox.

Came across the same issue. The container is only listening on port 80. `curl -k https://localhost` inside the container shows `Connection refused`.

I have restored the volumes from a backup in the meantime. I'm not sure if this is related to this issue, but `kubectl mayastor get volumes` shows one faulted volume:...

With that I get this: ``` {"details":"Storage Error: Volume Config for Resource id 94d6f5c7-9a07-4c27-9cdb-8b499783571b not committed to the store","kind":"FailedPersist"} ```