We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environmental Info: K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
This version update should fix the issue discussed in #9807 Describe the bug:
Steps To Reproduce:
#9807 (reply in thread)
Expected behavior:
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered:
Cluster nodes: ip-[redacted].us-east-2.compute.internal Ready control-plane,etcd,master 31s v1.29.4-rc1+k3s1 [redacted] [redacted] Ubuntu 22.04.1 LTS 5.15.0-1019-aws containerd://1.7.15-k3s1 journalctl -u k3s.service | grep "Starting network policy controller version" Apr 17 17:57:34 ip-[redacted] k3s[1992]: time="2024-04-17T17:57:34Z" level=info msg="Starting network policy controller version v2.1.0, built on 2024-04-16T23:18:20Z, go1.21.9" Apr 17 18:01:08 ip-[redacted] k3s[8767]: time="2024-04-17T18:01:08Z" level=info msg="Starting network policy controller version v2.1.0, built on 2024-04-16T23:18:20Z, go1.21.9"
Sorry, something went wrong.
rbrtbnfgl
endawkins
No branches or pull requests
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
This version update should fix the issue discussed in #9807
Describe the bug:
Steps To Reproduce:
#9807 (reply in thread)
Expected behavior:
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered: