Docs for --scheduler-override-broadcast-host-port#4721
Merged
Conversation
Signed-off-by: Albert Callarisa <[email protected]>
3 tasks
nelson-parente
approved these changes
Jul 18, 2025
marcduiker
requested changes
Jul 22, 2025
marcduiker
left a comment
marcduiker
left a comment
Contributor
There was a problem hiding this comment.
I've left two suggestions
| | `--container-runtime` | | `docker` | Used to pass in a different container runtime other than Docker. Supported container runtimes are: `docker`, `podman` | | ||
| | `--dev` | | | Creates Redis and Zipkin deployments when run in Kubernetes. | | ||
| | `--scheduler-volume` | | | Self-hosted only. Optionally, you can specify a volume for the scheduler service data directory. By default, without this flag, scheduler data is not persisted and not resilient to restarts. | | ||
| | `--scheduler-override-broadcast-host-port` | | | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. If not specified, it uses localhost:50006 (6060 for Windows). | |
Contributor
There was a problem hiding this comment.
Suggested change
| | `--scheduler-override-broadcast-host-port` | | | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. If not specified, it uses localhost:50006 (6060 for Windows). | | |
| | `--scheduler-override-broadcast-host-port` | | localhost:50006 (6060 for Windows) | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. | |
|
|
||
| This is necessary when you have to connect to the scheduler using a different host and port, as the scheduler only allows connections matching this host and port. | ||
|
|
||
| By default, the scheduler will use localhost:50006 (6060 for Windows), as it's the most common way to connect to the scheduler. |
Contributor
There was a problem hiding this comment.
Suggested change
| By default, the scheduler will use localhost:50006 (6060 for Windows), as it's the most common way to connect to the scheduler. | |
| By default, the scheduler will use localhost:50006 (6060 for Windows). |
Signed-off-by: Albert Callarisa <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Added docs for the new
dapr initself-hosted setting--scheduler-override-broadcast-host-port.Issue reference
Implementation PR (and 1.15 patch):
dapr/cli#1520
dapr/cli#1521