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

RFC 6598 #391

Open
davidmonk-cbts opened this issue Oct 27, 2023 · 7 comments
Open

RFC 6598 #391

davidmonk-cbts opened this issue Oct 27, 2023 · 7 comments

Comments

@davidmonk-cbts
Copy link

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
Copy link
Contributor

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
Copy link
Author

davidmonk-cbts commented Dec 1, 2023 via email

@SenthuranSivananthan
Copy link
Contributor

@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
Copy link
Contributor

tredell commented Dec 4, 2023

@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
Copy link
Author

davidmonk-cbts commented Dec 4, 2023 via email

@alenat10
Copy link

alenat10 commented Dec 4, 2023

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)

Copy link

github-actions bot commented Mar 4, 2024

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 github-actions bot added the stale label Mar 4, 2024
@skeeler skeeler removed the stale label Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants