You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
"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.
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?
The text was updated successfully, but these errors were encountered: