Page MenuHomeElementl

[helm] Adding configurable RunCoordinator (1/n)
ClosedPublic

Authored by sidkmenon on May 21 2021, 5:42 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 14, 1:29 AM
Unknown Object (File)
Sat, Mar 11, 12:25 AM
Unknown Object (File)
Thu, Mar 2, 3:35 AM
Unknown Object (File)
Feb 11 2023, 8:51 AM
Unknown Object (File)
Feb 9 2023, 1:32 PM
Unknown Object (File)
Feb 6 2023, 6:15 AM
Unknown Object (File)
Jan 24 2023, 6:53 PM
Unknown Object (File)
Jan 23 2023, 10:18 AM
Subscribers
None

Details

Summary

By adding a configurable RunCoordinator to the helm chart, users will able to accomplish run attribution or specify custom hooks when a run is submitted.

Test Plan

Added tests to ensure that new schema elements (i.e. RunCoordinator module/class etc.) render correctly.

Diff Detail

Repository
R1 dagster
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

sidkmenon held this revision as a draft.
sidkmenon edited the test plan for this revision. (Show Details)
This revision is now accepted and ready to land.Jun 1 2021, 3:39 PM

nit, should change the config name in values.yaml and the schema

helm/dagster/values.yaml
778

An alternative approach would be to to remove the 'enabled' field and switch to the pattern we're using for the run launcher- the DefaultRunCoordinator is equivalent to current enabled:false. I'm ok with this setup though.

Sid correctly pointed out that both of the above suggestions are breaking changes. He'll file an issue so that we can address in 0.12. lgtm