This message was deleted.

no, it is not. If you want it you should start k3s with

--kube-apiserver-arg=enable-admission-plugins=NodeRestriction,ResourceQuota

Thanks for the info.

hmm, actually, it looks like that doc is out of date from upstream. We don’t specifically enable it but it appears to be on by default in recent versions

So I don't need to pass the flag? It is already enbled by default in k3s?

not in k3s specifically, but just from looking at the logs it appears that the controller is started even if you don’t enable that admission plugin. So I’m not sure what upstream Kubernetes is doing at the moment.

Alright. Got it.