Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflowdefault configmap at the namespace level #14057

Open
shuangkun opened this issue Jan 8, 2025 · 0 comments
Open

Workflowdefault configmap at the namespace level #14057

shuangkun opened this issue Jan 8, 2025 · 0 comments
Labels
area/controller Controller issues, panics type/feature Feature request

Comments

@shuangkun
Copy link
Member

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

  1. The operation and maintenance team only wants to operate and maintain one argo instance and does not want to install argo in multiple namespaces
  2. 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 👍.

@shuangkun shuangkun added type/feature Feature request area/controller Controller issues, panics labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/controller Controller issues, panics type/feature Feature request
Projects
None yet
Development

No branches or pull requests

1 participant