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

Automated backport of #913: Use endpoints from Broker while validating overlapping CIDRs #951

Conversation

sridhargaddam
Copy link
Member

Backport of #913 on release-0.13.

#913: Use endpoints from Broker while validating overlapping CIDRs

For details on the backport process, see the backport requests page.

As part of the following PR[1], we no longer sync an endpoint
from the Broker if the endpoint has any overlapping CIDRs with the
local cluster. This was done to avoid issues on the Gateway node.
Consequently, the subctl diagnose code should ideally examine
the endpoints on Broker when validating overlapping CIDRs instead
of inspecting the endpoints on the local cluster. This PR addresses
this issue.

[1] submariner-io/submariner#2263

Signed-off-by: Sridhar Gaddam <[email protected]>
@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr951/sridhargaddam/automated-backport-of-#913-origin-release-0.13
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@tpantelis
Copy link
Contributor

This is a draft. Is it still needed?

@sridhargaddam
Copy link
Member Author

This is a draft. Is it still needed?

Some of the APIs were changed and I had to manually do the necessary changes.
Closing this in favor of #964

@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr951/sridhargaddam/automated-backport-of-#913-origin-release-0.13]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants