allow to specify encryption of the networking at create time when using kops and a network provider.
right now
kops create cluster {options} --networking weave creates an unecnrypted mode.
we should add an option to make it encrypted from the get-go
https://github.com/weaveworks-experiments/weave-kube/issues/38#issuecomment-253855874
by having kops create a password and add that line into the weave-net DS so we dont have to manually touch it and reroll the DS across the cluster.
We can have that as an option, but would rather not have that as default. does it use more resources and is it possibly slower?
Oh definitely make it as an option.
Doing encryption is inevitably slower than not doing it; as of 1.9.0 Weave Net can do it in the kernel which vastly reduces the overhead.
I believe there was just a PR submitted to pull 1.9 into the kops branch here https://github.com/kubernetes/kops/pull/1893#issuecomment-279725222
hello
just for avoid collision: i working in it.
thanks
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Most helpful comment
hello
just for avoid collision: i working in it.
thanks