fix: population of the schedulerhostaddress in self-hosted mode #1475
Conversation
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
The scheduler host address is pre-populated when using the self-hosted mode multi-app run similarly to the single app run. Kubernetes multi-app run is not affected and you will still need to specify a scheduler host address. Signed-off-by: mikeee <hey@mike.ee>
mikeee
force-pushed
the
bugfix/multi-app-scheduler-init
branch
from
d3417b7 to
47911f6
Compare
Signed-off-by: mikeee <hey@mike.ee>
yaron2
approved these changes
Jan 20, 2025
4 tasks
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The scheduler host address is pre-populated when using the self-hosted mode multi-app run similarly to the single app run. Kubernetes multi-app run is not affected and you will still need to specify a scheduler host address.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: