Update Calico from v3.6.1 to v3.7.0 #131
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
network_encapsulation
variable to choose whether the default IPPool should use ipip (default) or vxlan encapsulationnetwork_mtu
as the MTU for workload interfaces for ipip or vxlan (although Calico can have a IPPools with a mix, we're picking ipip xor vxlan)Note: Its an aim to allow Calico (VXLAN) in Typhoon Azure and DigitalOcean (potentially displacing the Flannel default). Typhoon GCP, AWS, and bare-metal already default to Calico (IPIP) and will continue using IPIP mode (preferred, non-optional).