-
Notifications
You must be signed in to change notification settings - Fork 670
Make weave-kube work with AWSVPC mode #2611
Comments
From @chrislovecnm on October 9, 2016 20:28 @bboreham more details on this please |
From @bboreham on October 9, 2016 20:55 https://www.weave.works/documentation/net-latest-using-weave/net-latest-awsvpc/ |
From @chrislovecnm on October 9, 2016 21:15
You want me to open another ticket about how to get around that?? That is a big concern of ours. |
From @chrislovecnm on October 9, 2016 22:46 Did not ask a good question ;) Can you run weave and get around the limit? Not run in aws vpc mode? Not sure if u have to use vpc mode. |
From @chrislovecnm on October 10, 2016 0:53 Perfect. Any idea how much of a performance hit you get with the overlay? I know native networking is always faster. |
From @bboreham on October 10, 2016 10:32 As always with performance, you should measure the real system you care about. However we posted some fairly simple benchmark numbers at https://www.weave.works/weave-fast-datapath/, and more graphically at https://www.weave.works/container-networking-no-overlay-aws-vpc/ |
The big thing is the 50 VM limit and can we upgrade or migrate between those patterns on the love cluster. I know this is a short statement. |
From @bboreham on October 8, 2016 21:15
This may be as simple as adding the flag, but will need testing, and all the setup preamble needs documenting.
Copied from original issue: weaveworks-experiments/weave-kube#31
The text was updated successfully, but these errors were encountered: