You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of v2.9, there is the ability to override the default artifact repository on a per-namespace basis by supplying a ConfigMap in said namespace with the appropriate label. However, it only works explicitly for setting the default-artifact-repository.
This request is to expend this feature for workflowDefaults.
When would you use this?
This would be particularly valuable in multi-tenancy environments were tenants may be assigned their own namespace for executing workflows. This would allow setting default annotations, labels, service account, etc. at the namespace level, allowing tenants to make smaller, more DRY workflows.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
What change needs making?
As of v2.9, there is the ability to override the default artifact repository on a per-namespace basis by supplying a ConfigMap in said namespace with the appropriate label. However, it only works explicitly for setting the
default-artifact-repository
.This request is to expend this feature for
workflowDefaults
.When would you use this?
This would be particularly valuable in multi-tenancy environments were tenants may be assigned their own namespace for executing workflows. This would allow setting default annotations, labels, service account, etc. at the namespace level, allowing tenants to make smaller, more DRY workflows.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: