CNI provider post #1
Conversation
chrislovecnm
force-pushed
the
cni-provider-post
branch
2 times, most recently
from
40fd3d8 to
77af2bf
Compare
| --- | ||
|
|
||
| Container Network Interface(CNI), is a library, under the umbrella of the Cloud | ||
| Native Computinmake -f NG.mk test version-distg Foundation project. Kubernetes |
There was a problem hiding this comment.
Multi-tasking .. yay
|
|
||
| > Which CNI provider should I use? | ||
|
|
||
| The above question is repeatedly ask on the #kops Kuberentes slack channel. |
| works anywhere VXLAN default, can be layered with Calico policy engine (Canal). | ||
| Oh, and lots of users. | ||
|
|
||
| Techtonics, CoreOS's Commercial Kuberentes product, uses a combination of |
There was a problem hiding this comment.
Typo in Tectonic and Kubernetes
|
|
||
| ### kube-router | ||
|
|
||
| Kuber-router is a purpose-built network solution for Kuberentes ground up. It |
There was a problem hiding this comment.
Kuber-router -> kube-router, Kuberentes -> Kubernetes
| Kuber-router is a purpose-built network solution for Kuberentes ground up. It | ||
| aims to provide operational simplicity and performance. Kube-router delivers a | ||
| pod networking solution, a service proxy, and network policy enforcer as | ||
| all-in-one solution, with single daemon set. Kuber-router uses Kubernetes native |
| Kubernetes Network Policy APIs and never uses an overlay, even when a cluster is | ||
| split across network availability zones. Romana is the only CNI provider that | ||
| uses native VPC networking across availability zones for HA clusters, delivering | ||
| a high-performance CNI solution. The current release uses its Etcd cluster, but |
There was a problem hiding this comment.
Does "its Etcd cluster" mean "its own dedicated etcd cluster"?
| <th>Network <br>Policies</th> | ||
| <th>Mesh</th> | ||
| <th>External <br>Database</th> | ||
| <th>Encyption</th> |
| Justin Santa Barbara the founder of kope-vxlan provided this: | ||
|
|
||
| Pioneered the model that everyone is now using, No baggage, with Minimal CNI | ||
| dependencies. Currently, there is lower adoption. |
There was a problem hiding this comment.
Ah well, if we're doing marketing speak.
"kopeio-networking provides kubernetes-first networking. It was purpose built for Kubernetes, making full use of the Kubernetes API, and because of that is much simpler and more reliable than alternatives that were retrofitted. The VXLAN approach is the most commonly used mode (as used in weave & flannel), but it also supports layer 2 (as used in calico), with more experimental support for GRE (the replacement for IPIP), and for IPSEC (for secure configurations). It does all of this with a very simple codebase."
| <tr> | ||
| <th>Provider</th> | ||
| <th>Network <br>Model</th> | ||
| <th>BGP</th> |
There was a problem hiding this comment.
Recommend dropping BGP from the comparison table - it's a bug, not a feature.
There was a problem hiding this comment.
ROTFL ... I may have to do a funny comments section
| <th>BGP</th> | ||
| <th>Network <br>Policies</th> | ||
| <th>Mesh</th> | ||
| <th>External <br>Database</th> |
There was a problem hiding this comment.
This one's tricky, because this a negative, right? I guess I would put "Datastore" and have 3 options "Kubernetes", "Mesh", or "BYO etcd".
|
|
||
| ## Summary | ||
|
|
||
| Pick one. Make a decision quickly, don't spend days deciding, and test with |
There was a problem hiding this comment.
Don't rule out kubenet. For most users, it remains the best choice.
|
|
||
| ### kopeio-vxlan | ||
|
|
||
| Justin Santa Barbara the founder of kope-vxlan provided this: |
There was a problem hiding this comment.
Might as well call it founder of kopeio for consistency.
| categories: kuberentes cni | ||
| --- | ||
|
|
||
| Container Network Interface(CNI), is a library, under the umbrella of the Cloud |
There was a problem hiding this comment.
I think it's an interface specification in the first place, which comes with a reference implementation in Go, and that consists of a library and a set of CLI utils.
chrislovecnm
force-pushed
the
cni-provider-post
branch
from
8c17381 to
1af979a
Compare
@justinsb @bboreham et al please take a look