Impersonating the controller's service account (kubectl proxy --port=8080 --as system:serviceaccount:kube-system:kubernetes-pfsense-controller) I have requested the same resources and while it's accessing /apis/extensions/v1beta1/ingresses just fine, I get a 403 when accessing /apis/networking.k8s.io/v1beta1/ingresses.
Impersonating the controller's service account (
kubectl proxy --port=8080 --as system:serviceaccount:kube-system:kubernetes-pfsense-controller
) I have requested the same resources and while it's accessing/apis/extensions/v1beta1/ingresses
just fine, I get a403
when accessing/apis/networking.k8s.io/v1beta1/ingresses
.With this change, it resolves fine!
Related issue: #3