-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Ignore known Kubernetes internal resources by default with resource.exclusions
#20013
Comments
To add my two cents: I would love to hide Endpoints and EndpointSlices from the UI, but only those that I did not directly deploy. For example, the kube-prometheus-stack deploys some Endpoint resources (for example when configuring the helm value |
@ChristianCiach +1 I think this would be a new feature that makes sense and it is not necessary to wait for 3.0 To implement / configure it:
Alternative:
Note that this has no improvements on performance, but it will improve the UX. |
Related #18857 |
@agaudreault have we identified any resources that we believe we can safely exclude by default (seems like there might be some concern about Endpoints/EndpointSlces)? |
Summary
Exclude
Endpoints
andEndpointSlices
by default.Motivation
Endpoints
andEndpointSlices
are Kubernetes internal resources that most users will never directly create. They can clutter the UI and decrease Argo performance due to high churn.Proposal
Specify the resources by default in the
resource.exclusions
configuration.The text was updated successfully, but these errors were encountered: