netscaler-k8s-node-controller icon indicating copy to clipboard operation
netscaler-k8s-node-controller copied to clipboard

[Feature] Use a kubernetesURL for node-controller to manage a diffent cluster.

Open BobVanB opened this issue 1 year ago • 2 comments

Feature request

We want to manage a remote user cluster that is owned by a customer. If we can connect the node-controller to a remote kubernetes cluster, than we can remove the workload on a that cluster. The node-controller has the credentials to the Citrix ADC. This way we don't have to find a way to hide these credentials.

The same functionality existst in the citrix-ingress-controller: https://github.com/citrix/citrix-helm-charts/blob/master/citrix-ingress-controller/values.yaml#L42

Current situation

Currently the situation is fixed for local development with a kubeconfig or inside a kubernetes cluster.

  • The namespace is pulled from /var/run/secrets inside the node-controller pod.
  • The k8s api connection has only 2 options build in to connect to kubernetes.
    1. The kubeconfig located at ~/.kube/config
    2. The in-cluster configuration is pulled from `/var/run/secrets inside de node-controller pod.

BobVanB avatar Sep 15 '23 12:09 BobVanB

Is there any progress with this feature request. We really would like this, it will solve our multicluster/multicustomer problem. With kind regards, Bob

BobVanB avatar Nov 03 '23 12:11 BobVanB

Hi Bob, We are discussing this thread over email and we are exploring CPX as an alternative option for your remote access setup. Let us know if you find any issues with adopting the suggested architecture.

mayurmohanpatil avatar Feb 21 '24 04:02 mayurmohanpatil