-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[ConnectedK8s] Add support for multiple proxy instances running on the same machine using different ports #7455
[ConnectedK8s] Add support for multiple proxy instances running on the same machine using different ports #7455
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @RyanBDB, |
ConnectedK8s |
Note, azdev style is failing, but the flagged issues are not par of the code changes in this PR. |
|
@darrendejaeger Could you please help review it again? |
[Release] Update index.json for extension [ connectedk8s ] : https://dev.azure.com/azclitools/release/_build/results?buildId=146822&view=results |
…e same machine using different ports (Azure#7455)
This PR addresses #6366
For our use case, it would be very helpful for the connectedk8s proxy to support multiple instances running on the same machine. This enables interactions/ control over multiple Arc connected Kubernetes clusters from the same machine by simply switching your kube context.
I've tested the change locally and been able to run multiple proxies on different ports and use kubectl to target multiple clusters by switching kube context.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az connectedk8s proxy
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json
.