https://dagster.io/ logo
#deployment-kubernetes
Title
# deployment-kubernetes
g

Guillaume Onfroy

03/21/2023, 10:38 AM
Hi. When deploying code locations via the helm chart (
dagster-user-deployments
), sensors in each individual deployments are triggered by all the jobs across all the deployments, regardless of the sensor parameters. The sensors are defined using
@run_status_sensor
, and
monitor_all_repositories
is NOT set (default is
False
), and
monitored_jobs
is set with a specific list of jobs. It's basically like if configuration doesn't change anything, and sensors are monitoring all jobs across all deployments no matter what. We can observe the same behaviour when using the official
dagster-slack
sensor from
make_slack_on_run_failure_sensor
.
👀 1
b

Beltra

03/23/2023, 8:58 AM
I have experienced similar problem, I am using the
run_status_sensor
and it is triggered for all the jobs and not just those listed as
monitored_jobs
p

prha

03/23/2023, 6:14 PM
Hi Beltra… looks like this is a bug (GH issue here ), if you want to follow along or add some details
5 Views