The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Has anyone else found that the tags for dagster k8s config are not respected for individual ops and don't override the job-level tags ?

Are you <https://docs.dagster.io/deployment/guides/kubernetes/customizing-your-deployment#kubernetes-configuration-on-individual-steps-in-a-run|running your ops as separate pods>? The default is to run all steps in one pod, and then the individual op resource requests are not propagated.

yes I want each op to be run as a separate pod

Actually seems like it's resolved with the newest redeploy <@U04TLNKNQ4F>, apologies for the false alarm