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

Choose Vnet and subnet from a different resource group #96

Closed
2 tasks done
sparsick opened this issue Jan 20, 2022 · 0 comments · Fixed by #98
Closed
2 tasks done

Choose Vnet and subnet from a different resource group #96

sparsick opened this issue Jan 20, 2022 · 0 comments · Fixed by #98

Comments

@sparsick
Copy link
Contributor

sparsick commented Jan 20, 2022

What feature do you want to see added?

When using private ip address, you have to specify a vnet and a subnet. Currently, the plugin only support vnet from the same resource group that also the container instance will be used. In some cases, the vnet is set up in a different resource group. Therefore, the name of the resource group should be possible to specify.

This new field could be optional. So the default behaviour is using the same resource group as the container instance will use.

Todo List:

  • Add new optional field Name of resource group
  • Extend the documentation

Upstream changes

No response

sparsick added a commit to sparsick/azure-container-agents-plugin that referenced this issue Jan 21, 2022
- update help text
sparsick added a commit to sparsick/azure-container-agents-plugin that referenced this issue Jan 21, 2022
sparsick added a commit to sparsick/azure-container-agents-plugin that referenced this issue Jan 21, 2022
sparsick added a commit to sparsick/azure-container-agents-plugin that referenced this issue Jan 21, 2022
@timja timja closed this as completed in #98 Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant