Closed mickael-decastro closed 1 year ago
@mickael-decastro could you please try without using
Hi,
thks for your quick reply.
Without Namespace it works ... but I would like to limit cic collection to a specific namesapace.
As of now, we don't support Role based CIC. You can run CIC in any namespace with cluster-role permissions
Thanks for the reply. Have you plan to add it to the road map ? Or something to limit CIC on a specific namespace ?
hi @mickael-decastro We have supported CIC with minimal privileges for a particular namespace with Role binding. Please refer below release notes for more detail. https://github.com/citrix/citrix-k8s-ingress-controller/releases/tag/1.28.2
Describe the bug the vpx-ci pod are in CrashLoopBackOff and we have a Rbac 403 error to access to /namespaces/{namespace}/version during citrix-k8s-ingress-controller deployment. Auto route configuration is enable and cic namespace set.
Slack Channel To request an invitation to participate in the Slack channel, please supply your email address using this form: https://podio.com/webforms/22979270/1633242
To Reproduce
Expected behavior
The vpx-cic pod should be start properly and create routes on external VPX appliance.
Logs kubectl logs cic-k8s-ingress-controller -n test-vpx
Additional context CIC configuration: