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

Network communication between two tier 3 vnets #634

Closed
brooke-hamilton opened this issue Feb 7, 2022 · 2 comments · Fixed by #926
Closed

Network communication between two tier 3 vnets #634

brooke-hamilton opened this issue Feb 7, 2022 · 2 comments · Fixed by #926
Assignees
Labels
bicep Related to Bicep code

Comments

@brooke-hamilton
Copy link
Contributor

brooke-hamilton commented Feb 7, 2022

Benefit/Result/Outcome

So that customers have clear guidance, and possibly some automation, to allow two tier 3 vnets to communicate with each other.

Description

Network traffic is enabled by default between every tier 3 vnet and tiers 0, 1, and 2. However, each tier 3 vnet cannot communicate with other tier 3 vnets by default. This work involves adding guidance to the tier 3 example explaining how to enable traffic between the vnets, and possibly some Bicep automation code.

Acceptance Criteria

  • Documentation exists in the tier 3 example README.md to describe how to enable traffic between two tier 3 vnets.
  • Optional: automation exists in the tier 3 example (either within the Bicep template or as an additional Bicep template).
  • If the optional automation (above) is not implemented with this work, then an AZ CLI command or commands should be shown in the tier 3 example README.md along with the documentation to show how to implement the settings.
@brooke-hamilton brooke-hamilton added spike A time-boxed effort to answer a question examples Related to content in the `src/bicep/examples` folder labels Feb 7, 2022
@brooke-hamilton
Copy link
Contributor Author

I will update the ACs on this to enable peering between every tier 3 and tiers 0, 1, 2.

@Phydeauxman is doing similar work - will consult with him on implementation.

@brooke-hamilton brooke-hamilton self-assigned this Feb 7, 2022
@brooke-hamilton brooke-hamilton moved this from Triage to Backlog in Mission Landing Zone 2022 Feb 7, 2022
@brooke-hamilton brooke-hamilton removed the spike A time-boxed effort to answer a question label Feb 9, 2022
@brooke-hamilton brooke-hamilton changed the title Network isolation for tier 3 spokes Network communication between two tier 3 vnets Feb 9, 2022
@brooke-hamilton brooke-hamilton removed their assignment Feb 9, 2022
@brooke-hamilton
Copy link
Contributor Author

I will update the ACs on this to enable peering between every tier 3 and tiers 0, 1, 2.

Done.

@brooke-hamilton brooke-hamilton self-assigned this Feb 10, 2022
@brooke-hamilton brooke-hamilton added the draft Issues that are being authored, not ready for adding to a release. label Feb 10, 2022
@jamasten jamasten added bicep Related to Bicep code and removed draft Issues that are being authored, not ready for adding to a release. examples Related to content in the `src/bicep/examples` folder labels Mar 9, 2024
@jamasten jamasten linked a pull request Mar 9, 2024 that will close this issue
@jamasten jamasten assigned jamasten and unassigned brooke-hamilton Apr 3, 2024
@jamasten jamasten added this to the March 2024 Sprint milestone Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bicep Related to Bicep code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants