Hi team! Is there a way to specify a Kubernetes config on an

@asset

materialization, just like I would in a job or op? Looking at the

@asset

params, we found the

op_tags

, but I'm not sure adding a mapping of

dagster-k8

config similar to the one on a job or op definition would work. cc: @Gabriel Montañola

To my knowledge, there is not. This is because unlike jobs, assets can be grouped many different ways for materialization, in ways that could cause conflicts for k8s tags. When I asked previously, I was advised to create my own jobs/sensors for now. I’ll see if I can find that discussion…