-
Notifications
You must be signed in to change notification settings - Fork 55
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
dev-docs: Helm chart for full L3 VPN connectivity #2620
Conversation
fyi: I rebased and merged my changes to main. So you should be able to re-base this PR now. |
b0521f8
to
13e7a64
Compare
✅ Deploy Preview for constellation-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
e0a3e70
to
2802477
Compare
2802477
to
2f6bf27
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested some setup where we either can also allow the node CIDR (since all pod traffic not destined for inside the cluster is usually masqueraded). Or, if we also want to preserve the pod IP we switch to eBPF based host routing (which we should anyway) and add a ip masq config which makes an exception for the peered range (https://docs.cilium.io/en/stable/network/concepts/masquerading/#ebpf-based)
I think it's best to simply discuss on Monday.
dev-docs/howto/vpn/helm/files/routing/experimental/frontend-pod.sh
Outdated
Show resolved
Hide resolved
dev-docs/howto/vpn/helm/files/routing/experimental/all-nodes.sh
Outdated
Show resolved
Hide resolved
c19425c
to
14c9ae2
Compare
14c9ae2
to
b945a49
Compare
Coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This already looks and works quite good. Just some advanced discussions. We cal also merge this at some point and discuss elsewhere.
63cd368
to
157cf12
Compare
157cf12
to
50796be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also note the comment in #2620 (comment)
dev-docs/howto/vpn/helm/files/routing/experimental/all-nodes.sh
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ef2fdca
to
3deb089
Compare
Context
Modifies the VPN Helm chart to allow for full bidirectional L3 connectivity.
Note: this PR targets the VPN development branch for now.
Checklist