-
Notifications
You must be signed in to change notification settings - Fork 388
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fail in Agent initialization if GRE tunnel type is used with IPv6
The 'gre' tunnel type does not work for IPv6 overlays. The correct tunnel type for OVS would be 'ip6gre'. For dual-stack clusters with both an IPv4 and an IPv6 overlay, we would need 2 default tunnel ports: one for IPv4 (with type 'gre') and one for IPv6 (with type 'ip6gre'). This would add complexity (and require testing) as the code currently assumes a single default tunnel port. Rather than trying to support IPv6 with the added complexity that it entails, we choose to fail during Agent initialization for now if the user-provided tunnel type is 'gre' and the cluster supports IPv6. Note that this means that the default manifest for IPsec (antrea-ipsec.yml) cannot be used in an IPv6 cluster as the tunnel type defaults to GRE in that case. However, this is not new, and it is better to fail explicitly rather than have a cluster where the Agent appears to be running fine but there is no connectivity. See #3150 Signed-off-by: Antonin Bas <abas@vmware.com>
- Loading branch information
1 parent
1d27432
commit 584782b
Showing
10 changed files
with
78 additions
and
47 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters