-
Notifications
You must be signed in to change notification settings - Fork 35
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement clusterset VIP for ServiceImports in LH agent (#1639)
As per https://github.com/submariner-io/enhancements/blob/devel/lighthouse/mcs-compliance.md Highlights: - The clusterset IP enabled flag and clusterset IP CIDR are passed vi env vars SUBMARINER_CLUSTERSET_IP_ENABLED and SUBMARINER_CLUSTERSET_IP_CIDR. - If no CIDR is passed, then clusterset IP functionality is disabled - Clusterset IP allocation is determined by the Serviceexport annotation "lighthouse.submariner.io/use-clusterset-ip" or, if not set, the global enablement flag. - Clusterset allocation is done only on creation of the aggregated ServiceImport. The "lighthouse.submariner.io/clusterset-ip-allocated-by" annotation is added by the allocating cluster. - The "lighthouse.submariner.io/use-clusterset-ip" annotation is always set on the aggregated ServiceImport. - If an exporting cluster's local clusterset enablement does not match the annotation setting on the aggregated ServiceImport, a "ConflictingClusterSetIPEnablement" Conflict condition is set. - If the allocating cluster's service is unexported, the ServiceImport's clusterset IP remains and is not release to the pool. - When a service is unexported from all clusters and the aggregated ServiceImport is deleted, the allocating cluster releases the clusterset IP back to the pool. - On restart, before starting the syncers, the controller iterates thru all the local aggregated ServiceImports and reserves any clusterset IPs that were allocated from its pool, ie that are in its CIDR range. Signed-off-by: Tom Pantelis <[email protected]> Co-authored-by: Yossi Boaron <[email protected]>
- Loading branch information
Showing
11 changed files
with
476 additions
and
44 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
Oops, something went wrong.