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

Backport of Added new remove the requirement for inbound network rules section into stable-website #5168

Conversation

hc-github-team-secure-boundary

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

@hc-github-team-secure-boundary hc-github-team-secure-boundary merged commit b9a771f into stable-website Oct 9, 2024
@hc-github-team-secure-boundary hc-github-team-secure-boundary deleted the backport/dannyknights_130824_branch/blatantly-winning-narwhal branch October 9, 2024 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants