Closed Arvintian closed 1 year ago
This is coming from something deep in the Kubernetes flow control code. I don't know what the impact of it is, or what it indicates. I would probably recommend opening an issue upstream; this is not something modified by or unique to K3s
Environmental Info: K3s Version:
k3s version v1.25.11+k3s1 (582f07cf) go version go1.19.10
Node(s) CPU architecture, OS, and Version:
Linux localhost 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Additional context / logs: