You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
When creating a provider gateway using IP Spaces one is able to configure specific T0 Interfaces for that uplink via the VCD UI.
New or Affected Resource(s)
vcd_ip_space_uplink
Terraform Configuration (if it applies)
Proposal of a new argument
associated_interfaces=[nsxt_policy_tier0_gateway_interface.internet01.id, nsxt_policy_tier0_gateway_interface.internet02.id] // Optional (VCD 10.5.1+) / If one or more interfaces are specified, then NAT, Firewall and routing settings using this IP-Space will only apply to those interfaces instead of all connected interfaces. Default: []
References
The text was updated successfully, but these errors were encountered:
@Didainius yes, I am planning to implement this in our stack. It may take some time though...
Got it, thanks. So we have working tests as usual and it all should be good, but whenever possible, your feedback is very valuable. If you get a chance to try - do post if it worked for you.
Community Note
Description
When creating a provider gateway using IP Spaces one is able to configure specific T0 Interfaces for that uplink via the VCD UI.
New or Affected Resource(s)
Terraform Configuration (if it applies)
Proposal of a new argument
References
The text was updated successfully, but these errors were encountered: