Azure/CanadaPubSecALZ

RFC 6598

davidmonk-cbts opened this issue · 8 comments

davidmonk-cbts commented

Is there a way to have a deployment of this configuration without any utilization of the 6598 space? At this time, a customer we have will have this Azure deployment with no inter-department or external connections at all.

SenthuranSivananthan commented

You can deploy without the 6598 address space. The VNET address spaces are array input (in the parameters.json file), therefore you can just add RFC 1918 spaces.

davidmonk-cbts commented
  • 👍1
SenthuranSivananthan commented

@tredell wondering if there's a way to make RFC 6598 references optional? Do you have a suggestion?

@dmonkcbts, in the interim, you may have to comment out those lines in the Bicep and create a custom implementation for your requirements.

tredell commented

@dmonkcbts is the identity deployment failing on the UDR configuration?

If yes, we can try splitting out 'SpokeUdrHubRFC6598FWRoute' config (lines 208-216 in the Identity networking bicep file) and making it a conditional union based on if the variable is blank "" or has an IP range in it.

davidmonk-cbts commented
alenat10 commented

The parameter is set as required in line 137 in schema for Identity archetype.

And yes, as David mentioned if we try to omit the parameter the deployment fails on schema verification (obviously)

github-actions commented

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions commented

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.