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

Allow overriding the broker API endpoint URL #1017

Merged
merged 3 commits into from
Dec 6, 2023

Conversation

skitt
Copy link
Member

@skitt skitt commented Nov 30, 2023

In some setups, the broker URL determined from the kubeconfig context isn't usable from the clusters which will be joined. For these setups, the broker URL needs to be overridden, and this implements that by adding a --broker-url option to the following subctl sub-commands:

  • deploy-broker, to override the URL stored in the generated broker-info.subm file
  • recover-broker-info, for the same reason
  • join, to override the URL retrieved from the broker-info.subm file

Thus when the user knows ahead of time that the broker URL needs to be manually specified, they can provide the correct setting to deploy-broker, and join works as before. If they didn't know when deploy-broker was run, they can specify the correct URL when joining clusters. This also handles setups where each joining cluster might need a different URL to reach the broker.

Fixes: #300

deploy-broker doesn't have any sub-commands, flags shouldn't be
persistent.

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

🤖 Created branch: z_pr1017/skitt/override-broker-url
🚀 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.

@skitt skitt added the release-note-needed Should be mentioned in the release notes label Nov 30, 2023
In some setups, the broker URL determined from the kubeconfig context
isn't usable from the clusters which will be joined. For these setups,
the broker URL needs to be overridden, and this implements that by
adding a --broker-url option to the following subctl sub-commands:

* deploy-broker, to override the URL stored in the generated
  broker-info.subm file
* recover-broker-info, for the same reason
* join, to override the URL retrieved from the broker-info.subm file

Thus when the user knows ahead of time that the broker URL needs to be
manually specified, they can provide the correct setting to
deploy-broker, and join works as before. If they didn't know when
deploy-broker was run, they can specify the correct URL when joining
clusters. This also handles setups where each joining cluster might
need a different URL to reach the broker.

Signed-off-by: Stephen Kitt <[email protected]>
@skitt skitt force-pushed the override-broker-url branch from 43974a5 to 9ba3464 Compare November 30, 2023 12:55
@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Dec 4, 2023
@tpantelis tpantelis enabled auto-merge (rebase) December 6, 2023 22:11
@tpantelis tpantelis merged commit 20b752b into submariner-io:devel Dec 6, 2023
28 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr1017/skitt/override-broker-url]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-test When a PR is ready for full E2E testing release-note-handled release-note-needed Should be mentioned in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow specifying the broker API endpoint
4 participants