-
Notifications
You must be signed in to change notification settings - Fork 369
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use reserved OVS controller ports for default Antrea ports
Tunnel port, gateway port and uplink port. These reserved port numbers (starting from 32,768) will never be auto-assigned by OVS. By using them, we can avoid surprising ofport changes in some edge cases. Note that if these ports already exist when the Agent starts, we will not re-create them or mutate their ofport. The new ofport values will only be used when creating the OVS ports for the first time (e.g., on a new K8s Node, or after a Node restart). That is the simplest solution and is consistent with existing behavior. It should also be sufficient for avoiding #6192, which was typically triggered by creating a new tunnel port when updating the Antrea configuration in an existing cluster. After this change, we will also assume that br-int ports stored in OVSDB always have the "antrea-type" external ID. This external ID became required in Antrea v1.5, so this should be an acceptable change, especially considering that this change is destined for the Antrea v2 release, which is a major version bump. Users will not be able to upgrade from Antrea v1.5 to Antrea v2.0, but that this is not a supported upgrade path anyway (for other reasons). We also add some logic to prevent creating a port on the OVS bridge if a required external ID is missing. Fixes #6192 Signed-off-by: Antonin Bas <[email protected]>
- Loading branch information
1 parent
6793694
commit 0733d0c
Showing
31 changed files
with
343 additions
and
351 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
Oops, something went wrong.