Struggling to create a NAT Gateway that can handle multiple public IP addresses #13837
ameltzer-MSFT
started this conversation in
Authoring Help
Replies: 1 comment
-
Not sure if this helps? Not that familiar with your issue, however I have used this extensively in the past. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is related to bug #13774. I figured I'd also open a companion discussion here to make sure I'm not doing something fundamentally wrong.
Here's the scenario I'm trying to accomplish:
I'm trying to set up a private VNET for some resources along with a NAT Gateway and Public IP for those things I want to have outbound Internet access. Finally, I need to bind that public IP to one or more roles.
I'm trying to modularize this as much as possible.
What does seem to work is if I create the public IP and NAT Gateway in one shot:
What is not working is if I try to do one of the following:
existing
) toproperties.publicIpAddresses
existing
) toproperties.natGateway
For instance, this does not work at all:
Nor does this:
In either case,
--what-if
confirms that theexisting
resource is completely ignored and the associated property isx
'ed out.I'm trying to have this as modular as possible so I can do things like add multiple public IPs to a single NAT Gateway, or associate a public IP with another role separately from creating it. Neither of these things seems possible today because the
existing
resource is simply ignored.Am I just making a fundamental mistake, or is there something actually wrong here?
Beta Was this translation helpful? Give feedback.
All reactions