Backport of Added new remove the requirement for inbound network rules section into stable-website #5168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #5010 to be assessed for backporting due to the inclusion of the label backport/website.
The below text is copied from the body of the original PR.
I was unaware until a few weeks ago, after speaking with @jefferai about the pure power of mhop and outbound connectivity. A question that comes up often is that if you have a mhop deployment and maybe a firewall in between, my understanding was that you would have to allow inbound connectivity to the egress worker associated with the target. After speaking with engineering, this is not the case.
I believe most, if not all of the field are unaware of this and it is a powerful feature. I think more needs to be made of it to highlight this. Certainly colleagues I've spoken to are unaware of it.
This PR is a draft for further review and discussion.
Overview of commits
4d17696
d067f3b
5b1c64f
f45a588
a0a21f8
f295c45