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

Gateway private network #1924

Merged
merged 7 commits into from
Mar 14, 2023
Merged

Gateway private network #1924

merged 7 commits into from
Mar 14, 2023

Conversation

muhamadazmy
Copy link
Member

Fixes #1674

  • Add optional network. If set the gateway can then proxy traffic to that network. Which means user can gateway traffic to a private workload that lives inside this network.
  • Backward compatible with older configurations, user can still use yggdrasil backends although not recommended for reliability
  • Fix few issues in gateway start up. specially after node reboot.

Move config files to volatile storage
because on node reboot, the gw config will be re-applied
anyway
LeeSmet
LeeSmet previously approved these changes Mar 14, 2023
Copy link
Contributor

@LeeSmet LeeSmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

cl zbus.Client
resolver *net.Resolver
sub substrate.Manager
// maps domain to workload id
reservedDomains map[string]string
domainLock sync.RWMutex

proxyConfigPath string
//proxyConfigPath string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover commented code

@muhamadazmy muhamadazmy merged commit 1221f02 into main Mar 14, 2023
@muhamadazmy muhamadazmy deleted the gateway-priv-network branch March 14, 2023 14:29
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

Successfully merging this pull request may close these issues.

proxy gateway traffic into private networks (over wireguard)
2 participants