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 #1653: E2E: use ServiceDiscovery CR to determine if clusterset IP is #1654

Conversation

tpantelis
Copy link
Contributor

Backport of #1653 on release-0.19.

#1653: E2E: use ServiceDiscovery CR to determine if clusterset IP is

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

...in E2E tests coz lighthouse agent may not be present if
service-discovery is disabled.

Signed-off-by: Vishal Thapar <[email protected]>
Signed-off-by: Tom Pantelis <[email protected]>
@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr1654/tpantelis/automated-backport-of-#1653-upstream-release-0.19
🚀 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 tpantelis enabled auto-merge (rebase) October 2, 2024 03:57
@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Oct 2, 2024
@tpantelis tpantelis merged commit ea9fb6e into submariner-io:release-0.19 Oct 2, 2024
29 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr1654/tpantelis/automated-backport-of-#1653-upstream-release-0.19]

@tpantelis tpantelis deleted the automated-backport-of-#1653-upstream-release-0.19 branch December 5, 2024 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated-backport ready-to-test When a PR is ready for full E2E testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants