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
Is your feature request related to a problem? Please describe.
NGINX Cluster Connector is a Kubernetes controller that connects to the NGINX Management Suite and reports the number of NGINX Ingress Controller nodes in the cluster. The NGINX Cluster Connector is deployed as a Kubernetes Deployment.
Which means that we have one more controller to configure and deploy.
Describe the solution you'd like
As an user I want an integrated experience without the need to deploy a separated controller, the connector functionality is part of NIC.
ensure that when multiple NIC deployments in a single cluster report that they do not overwrite each other
Now that we are implementing #5385 we can close this issue. Will wait for the upcoming refinement meeting before do that. Leaving this comment here as a reminder.
Is your feature request related to a problem? Please describe.
NGINX Cluster Connector is a Kubernetes controller that connects to the NGINX Management Suite and reports the number of NGINX Ingress Controller nodes in the cluster. The NGINX Cluster Connector is deployed as a Kubernetes Deployment.
Which means that we have one more controller to configure and deploy.
Describe the solution you'd like
Additional context
https://github.com/nginxinc/nginx-cluster-connector
The text was updated successfully, but these errors were encountered: