Azure / Azure/BatchExplorer

Private VNET address should be selectable

Open
#2,117 0 comments 0 reactions 0 assignees View on GitHub
:world_map: feature
Dominant language
TypeScript
Stars
205
Forks
75
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When running Batch Explorer on a locked down private VNET, the connection dialogue defaults to a public load balancer address which is not reachable from the private VNET, rendering this convenience feature inert.

**To Reproduce**
Create a private VNET, standup Batch explorer on a node in that network, deploy a batch pool into it and attempt to connect directly to pool nodes.

**Expected behavior**
Expected Batch Explorer to default to the private VNET associated with the batch pool, or perhaps offer it as an option / make it switchable between the networks.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.