This message was deleted.
# general
a
This message was deleted.
h
That would be for K8s, yes. In K8s, you activate an AdmissionController web hook in an argument to kube-apiserver. K3s, if I’m understanding right, uses a different mechanism for configuring the API server process. Where does K3s document this for admission control?
c
we use the same mechanism, its just embedded in the main K3s process. If you look at the k3s logs, you’ll see an entry about “running kube-apiserver” with all the apiserver flags that are being used all printed out. You can also add you own flags with the --kube-apiserver-arg option.
h
Thanks. I’l try that out. Now I need to find the k3s logs 🙂