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

Allow Calico networking on Azure and DigitalOcean #472

Merged
merged 1 commit into from
May 20, 2019
Merged

Conversation

dghubble
Copy link
Member

  • Introduce "calico" as a networking option on Azure and DigitalOcean using Calico's new VXLAN support (similar to flannel). Flannel remains the default on these platforms for now.
  • Historically, DigitalOcean and Azure only allowed Flannel as the CNI provider, since those platforms don't support IPIP traffic that was previously required for Calico.
  • Looking forward, its desireable for Calico to become the default across Typhoon clusters, since it provides NetworkPolicy and a consistent experience
  • No changes to AWS, GCP, or bare-metal where Calico remains the default CNI provider. On these platforms, IPIP mode will always be used, since its available and more performant than vxlan

@dghubble
Copy link
Member Author

dghubble commented May 20, 2019

I'm documenting use of Calico on Azure and DigitalOcean (i.e. VXLAN) mode as experimental. It does work, but my sense from testing is that this is quite early. On DigitalOcean, I've seen Calico restart a decent amount and raise node resource usage. On Azure, I've seen variable bandwidth, but some of this is hard to isolate from the lower reliability/consistency of Azure itself.

Officially, Azure and DO aren't marked as stable and this feature is marked as experimental. I feel alright about it. I'll be using the new Calico mode over coming weeks and see how it fares.

Calico (IPIP) remains as stable and reliable as ever on AWS, GCP, and bare-metal.

* Introduce "calico" as a `networking` option on Azure and DigitalOcean
using Calico's new VXLAN support (similar to flannel). Flannel remains
the default on these platforms for now.
* Historically, DigitalOcean and Azure only allowed Flannel as the
CNI provider, since those platforms don't support IPIP traffic that
was previously required for Calico.
* Looking forward, its desireable for Calico to become the default
across Typhoon clusters, since it provides NetworkPolicy and a
consistent experience
* No changes to AWS, GCP, or bare-metal where Calico remains the
default CNI provider. On these platforms, IPIP mode will always
be used, since its available and more performant than vxlan
@dghubble dghubble merged commit 147c21a into master May 20, 2019
@dghubble dghubble deleted the calico-vxlan branch May 20, 2019 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant