Skip to content

cic not export routes to Netscaler (rbacRole True) #681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ofaruk89 opened this issue Feb 25, 2025 · 2 comments
Open

cic not export routes to Netscaler (rbacRole True) #681

ofaruk89 opened this issue Feb 25, 2025 · 2 comments

Comments

@ofaruk89
Copy link

Version 1.43.7

When we set rbacRole to true, CIC does not export routes to netscaler. When we set rbacRole to false, it sends routes to netscaler, but since it discovers all namespaces, it puts a lot of pressure on the cluster API and causes the system to crash. How can we solve the route problem when rbacRole is in true mode?

@sivakumarpcitrix
Copy link

"routes to netscaler.", does it mean node related ip addresses added as routes in NetScaler?
If so, under RBAC role: CIC can't listen to cluster level resource related events. So, node level information will not be served.

May I know more details on "lot of pressure on the cluster API"?
if you are looking at number of api call's made to Kubernetes-API, you may un-install unwanted CRD's (like fetch CRD's with citrix.com and un-install/delete them), it should reduce the number of API-calls.

May I know customer/company details...

@subashd
Copy link
Collaborator

subashd commented Mar 17, 2025

hi @ofaruk89
Please provide the logs for troubleshooting and also could you please fill the questionaires?

Regards,
Subash Dangol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants