You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To mirror Derek's question, where's the acual problem? You didn't show kubectl get node -o wide, logs from the affected nodes, or anything else to back up your report that some nodes are unable to run. Did you at some point attempt to add additional nodes to this cluster?
Environmental Info:
K3s Version:
k3s version v1.27.4+k3s1 (36645e7)
go version go1.20.6
Node(s) CPU architecture, OS, and Version:
Linux hans 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
Currently, only 1 server is started
Describe the bug:
Some nodes have been unable to start after running. Enter kubectl all - n kube system
Steps To Reproduce:
Expected behavior:
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered: