Skip to content
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

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

Open
BobVanB opened this issue Sep 15, 2023 · 2 comments

Comments

@BobVanB
Copy link

BobVanB commented Sep 15, 2023

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 BobVanB changed the title [Feature] Change the kubernetesURL for node-controller to manage a diffent cluster. [Feature] Use a kubernetesURL for node-controller to manage a diffent cluster. Sep 29, 2023
@BobVanB
Copy link
Author

BobVanB commented Nov 3, 2023

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

@mayurmohanpatil
Copy link

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.

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

2 participants