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

Cannot run 2 instances of "az connectedk8s proxy" on the same VM #6366

Open
dschveninger opened this issue Jun 5, 2023 · 6 comments
Open
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. Connected Kubernetes needs-team-attention This issue needs attention from Azure service team or SDK team Service Attention This issue is responsible by Azure service team.

Comments

@dschveninger
Copy link

Describe the bug

The "az connectedk8s proxy" does not allow a client proxy to run more than one instance on a VM. We would like to be able to run multiple proxies by specifying client port number.

The following code prohibit the "az connectedk8s proxy" from running multi-instances on a VM.

The code only allows a single process running:

  1. Does not allow the Client port to be set.
    if(clientproxyutils.check_process(proc_name)):
  2. Check for a process name only.

What is the process for getting an idea like this evaluated?

Related command

None

Errors

Another instance of proxy already running

Issue script & Debug output

none

Expected behavior

Allow to specify client port and run instance of proxy on different local ports against different clusters.

Environment Summary

dschveninger@LAPTOP-GLS580EI:~/nc-scripts$ az --version
azure-cli 2.39.0 *

core 2.39.0 *
telemetry 1.0.6 *

Extensions:
connectedmachine 0.5.1
connectedk8s 1.3.13
azure-devops 0.25.0
k8s-extension 1.4.1
networkcloud 0.1.7.post234
customlocation 0.1.3
hybridaks 0.1.3

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Python location '/opt/az/bin/python3'
Extensions directory '/home/dschveninger/.azure/cliextensions'

Python (Linux) 3.10.5 (main, Jul 29 2022, 03:26:59) [GCC 9.4.0]

Legal docs and information: aka.ms/AzureCliLegal

Additional context

No response

@dschveninger dschveninger added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jun 5, 2023
@ghost ghost added Auto-Assign Auto assign by bot Connected Kubernetes CXP Attention This issue is handled by CXP team. labels Jun 5, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented Jun 5, 2023

Thank you for opening this issue, we will look into it.

@navba-MSFT navba-MSFT added Service Attention This issue is responsible by Azure service team. needs-team-attention This issue needs attention from Azure service team or SDK team and removed CXP Attention This issue is handled by CXP team. labels Jun 6, 2023
@navba-MSFT
Copy link
Contributor

non-customer reported. Adding Service team to look into this.

@phillipleblanc
Copy link

This would be very useful for us as well.

@pa654321
Copy link

pa654321 commented Mar 5, 2024

As an AON customer resolving this issue would be very helpful to us as well.

@maroxana
Copy link

maroxana commented Mar 7, 2024

Any update on this? Would be very helpful for "az connectedk8s proxy" to run multi-instances on a VM

@RyanBDB
Copy link
Contributor

RyanBDB commented Jun 7, 2024

Starting with extension version 1.6.8, you should now be able to run multiple instances of az connectedk8s proxy on the same VM if you specify different ports for each. You can do this using the --port argument. Note, the proxy will also use an internal port, which will continue to use the default for the first proxy instance you create, but will then pick the port numbered 1 less than the option you specify with the --port argument for subsequent proxy instances.

Note, you will then need to set the kube context to the cluster you want to target to change which proxy is being used/ which cluster you are targeting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. Connected Kubernetes needs-team-attention This issue needs attention from Azure service team or SDK team Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

7 participants