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

Prevent /applications page from loading on large installations #21830

Open
dee-kryvenko opened this issue Feb 10, 2025 · 0 comments
Open

Prevent /applications page from loading on large installations #21830

dee-kryvenko opened this issue Feb 10, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@dee-kryvenko
Copy link

Summary

Add an option to disable /applications page without either a project and/or a namespace filter.

Motivation

On a large ArgoCD instances with 10k+ apps, the /applications landing page becomes basically unusable. Nor does it makes any sense. No one ever will act or perform bulk actions on 10k+ apps anyways. For people who do not understand how ArgoCD works, it makes them think that ArgoCD is bad or can't scale or having issues. By extension, it casts a shadow on the team that maintains ArgoCD instance unjustifiably. Although that in my opinion it's not an issue, or at least is not an actionable one and does not indicate any underlying issues with the platform. Kubectl will also suffer if someone does --all-namespaces action, and its not a default behavior for a good reason. From my experience, people often having no clue that their quality can be drastically improved should only they follow a simple practice of NOT visiting ArgoCD landing page without at least one filter being activated. Even when I have to switch filters, for example - switch to another project, I would usually select another project first and then and only then unselect the previous project. If I ever forget to do it - congrats to me, I just suddenly got extra time for an extra cup of coffee.

Proposal

For example, just pick a first project on the list if no filters are set. Or, if feature is enabled, and no filters are set - display a placeholder empty page with a message or something. Last filter selection is already being remembered in the browser, no need to store anything additionally. No need to enforce this on the backend neither - being purely a quality of life for the end user improvement, this can be just a UI only feature. Probably doesn't even need explicit configuration option - UI can just see that the apps count is > X, and bail out. Really don't care how exactly it will be done, just that this pretty small and insignificant issue creates too much noise and talks about platform in general.

@dee-kryvenko dee-kryvenko added the enhancement New feature or request label Feb 10, 2025
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

1 participant