-
Notifications
You must be signed in to change notification settings - Fork 207
feat: Allow configuring the scheduler host on init #1520
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
feat: Allow configuring the scheduler host on init #1520
Conversation
Signed-off-by: Albert Callarisa <albert@diagrid.io>
JoshVanL
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's also backport this to release-1.15 and create a patch release.
Signed-off-by: Albert Callarisa <albert@diagrid.io>
5263b25 to
847ed81
Compare
Signed-off-by: Albert Callarisa <albert@diagrid.io>
72d8a7c to
d4731e5
Compare
|
Patch PR here: #1521 |
|
@acroca tests are failing |
|
@acroca - Please raise a PR for Dapr docs. |
@msfussell Thanks for reminding updating the docs :) dapr/docs#4721 |
|
@holopin-bot @acroca Here's a digital badge as a small token of appreciation. |
|
Congratulations @acroca, the maintainer of this repository has issued you a badge! Here it is: https://holopin.io/claim/cmi4ezotd000cjw04sbkp3nu8 This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Description
Added a new flag for
dapr initwhere the user can specify the scheduler host.This allows running dapr apps pointing to a remote scheduler, as long as the configured scheduler host address is reachable from the dapr app.
To test this feature, I have a container with
dindanddapr, where I executed:Then from another container with access to the docker instance from dind, I'm running a service with:
dapr run --app-id=test \ --metrics-port=9091 \ --scheduler-host-address=dind-service:50006 \ --placement-host-address=dind-service:50005 \ --dapr-grpc-port 50001 \ --app-port 50070 \ --app-protocol grpc \ --log-level debug \ go run .With this change, I see the following logs:
Without this change, it failed:
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: #1518
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: