https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
p
Copy code
k3s kubectl create ns foo
sleep 10
k3s kubectl delete ns foo
That triggers the issue for me on a fresh installed k3s
Does anyone have any idea why this may be happening?
Ah, firewall, nevermind. :-)
r
🤔 out of curiosity, how this issue was firewall related?
p
It seems firewalld was blocking one specific port that may be used by k3s?
So, maybe, that could be solved during k3s installation?
The reproducer is quite simple, fresh install, from the guide, on the latest CentOS 9 Stream
r
Got it, thank you.
c
It means your metrics server deployment is broken because the apiserver can't contact the metrics server pod to complete aggregated API discovery.
p
it's a single node server
c
Check the documentation. It is recommended to turn off the host-based firewall, if you must keep it running there are suggestions on what ports and IP ranges to open.
That doesn't make any difference
Until API discovery is complete, you can't delete namespaces because the apiserver cannot confirm that all resources have been removed from it.
👆 1
p
I see, yeah, I ended up turning off the firewall
It was just an "oh, wth???" kind of moment, as I never faced any issues with the ubuntu machines I've been using (same version of k3s and yatta yatta as the one I faced the issue on CentOS)
And it took me a while to remember firewalld was up and running on that machine
2 Views
Open in Slack
PreviousNext
Powered by