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

Promote Applications in Any Namespace to Stable #16189

Open
gnunn1 opened this issue Oct 31, 2023 · 7 comments
Open

Promote Applications in Any Namespace to Stable #16189

gnunn1 opened this issue Oct 31, 2023 · 7 comments
Labels
enhancement New feature or request
Milestone

Comments

@gnunn1
Copy link

gnunn1 commented Oct 31, 2023

Summary

Promote Application in Any Namespace from Beta to Stable

Motivation

The Applications in Any Namespace feature was introduced in 2.5 and since then considerable work has been done to correct outstanding issues. At the moment there are a handful of issues and none of them appear to be of the showstopping variety.

This feature has been widely adopted by the community as it addresses some significant limitations with operating Argo CD in a multi-tenant environment. This broad adoption belies it's Beta status and strengthens the argument that it should be promoted to a Stable feature.

Proposal

Applications in Any Namespace should be promoted to Stable where it makes sense with the Argo release cycle, ideally as part of the current 2.9 release cycle but worse case 2.10.

@gnunn1 gnunn1 added the enhancement New feature or request label Oct 31, 2023
@crenshaw-dev
Copy link
Member

I'm in support of this. The feature seems to be behaving well.

@jannfis
Copy link
Member

jannfis commented Nov 2, 2023

Agreed. I believe most of the early childhood flaws have been remedied as of now. I'd have a good feeling promoting it to stable.

@crenshaw-dev
Copy link
Member

We should probably make sure appsets-in-any-namespace is still marked alpha or beta.

@jannfis
Copy link
Member

jannfis commented Nov 2, 2023

One thing that I (and potentially others) have overlooked, there is no way yet to configure this via CLI or UI, I believe.

@ishitasequeira ishitasequeira added this to the v2.10 milestone Nov 14, 2023
@gnunn1
Copy link
Author

gnunn1 commented Feb 5, 2024

As an FYI, I think the CLI and UI are both there now?

Merged PR for UI: #16249
Code for CLI (As part of Apps in Any Namespace original PR from @jannfis): #9755

@mjgallag
Copy link

mjgallag commented May 7, 2024

Just wanted to call this issue out in case it might affect this decision but I don't have a strong opinion as to whether it should. I actually prefer the workaround but it initially caused confusion and took some time to figure out what was going on.

@agaudreault
Copy link
Member

+1 If everything is ready here, we just need a kind soul to open a PR and update all the doc related to this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants