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

Jump to bottom

[Feature] ipsec for Flannel and k3sup install #116

Open
alexellis opened this issue Dec 3, 2019 · 0 comments
Open

[Feature] ipsec for Flannel and k3sup install #116

alexellis opened this issue Dec 3, 2019 · 0 comments
Labels
feature/approved good first issue help wanted moscow/should-have size/m

Comments

@alexellis
Copy link
Owner

@alexellis alexellis commented Dec 3, 2019

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as per Darren's comment (@ibuildthecloud) here -> https://twitter.com/ibuildthecloud/status/1200119925500592129

Current Behaviour

k3s cannot be used on Packet.com due to the way flannel has no authentication and Packet.com has no firewall available.

Possible Solution

  • Add the flag to the install.go file.
  • Work out what parameter is required in the installer script and make that change
  • Check that agents can still join in this mode

https://rancher.com/docs/k3s/latest/en/installation/install-options/
k3s-io/k3s#951
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature/approved good first issue help wanted moscow/should-have size/m
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexellis