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

Update Calico from v3.1.3 to v3.2.1 #278

Merged
merged 1 commit into from
Aug 26, 2018
Merged

Update Calico from v3.1.3 to v3.2.1 #278

merged 1 commit into from
Aug 26, 2018

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Aug 15, 2018

@dghubble
Copy link
Member Author

dghubble commented Aug 19, 2018

Typhoon publishes expected pod-to-pod network performance details. A Typhoon AWS v1.11.2 cluster with Calico v3.1.3 nearly saturates the link with pod-to-pod bandwidth of ~980MB/s (range 950-1000MB/s) when using an 8981 MTU on a suitable instance. Testing Calico v3.2.0, with both MTU 1480 and 8981 shows only 400-500MB/s.

This update is on hold.

@dghubble dghubble changed the title Update Calico from v3.1.3 to v3.2.0 Update Calico from v3.1.3 to v3.2.1 Aug 25, 2018
@dghubble dghubble force-pushed the calico-update branch 2 times, most recently from 0dd3cf9 to af6bad9 Compare August 26, 2018 00:51
* Add new bird and felix readiness checks
* Read MTU from ConfigMap veth_mtu
* Add RBAC read for serviceaccounts
* Remove invalid description from CRDs
@dghubble
Copy link
Member Author

This was totally unrelated to Calico itself. A stray colon in value:From (now corrected to valueFrom) in the Calico Daemonset in poseidon/terraform-render-bootstrap#74 meant the IPIP MTU was left empty. Performance on Google Cloud was as good as expected (bc the default is 1440), whereas AWS needs a custom MTU for best results. The typo has been corrected and performance matches expectations.

@dghubble dghubble merged commit 7eb0923 into master Aug 26, 2018
@dghubble dghubble deleted the calico-update branch September 3, 2018 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant