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
Now workflowdefault is global, and the operation and maintenance team hopes to configure workflow default at the namespace level, just like artifacts.
Use Cases
The operation and maintenance team only wants to operate and maintain one argo instance and does not want to install argo in multiple namespaces
Support multiple business parties in different namespace,
a. For example, CI/CD business, using CI namespace, requires global labeling of CI tags to facilitate statistics of metrics.
b. Data business, using data namespace, requires all pods to inject initcontaienr to prepare data.
c. ML business, using ml namespace, requires all pods to inject a sidecar.
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
Now workflowdefault is global, and the operation and maintenance team hopes to configure workflow default at the namespace level, just like artifacts.
Use Cases
a. For example, CI/CD business, using CI namespace, requires global labeling of CI tags to facilitate statistics of metrics.
b. Data business, using data namespace, requires all pods to inject initcontaienr to prepare data.
c. ML business, using ml namespace, requires all pods to inject a sidecar.
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: