Ignore known Kubernetes internal resources by default with resource.exclusions

[agaudreault]

Summary

Exclude Endpoints and EndpointSlices by default.

Motivation

Endpoints and EndpointSlices 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.

[ChristianCiach]

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 kubeEtcd.endpoints) that I absolutely want to see in the UI. But the transitive EPs and EPSlices automatically created by Kubernetes for Services with selectors are annoying and clutter the UI.

[agaudreault]

@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:

• resources.exclusions should not include Endpoints
• add a new resources.hide ??? (better names are welcomed!)
  • configure endpoint/endpoint slices the same way it would have been configured in resources.exclusions
• Argo does not add the resource to the Application resource tree / UI when
  • resource is included in resources.hide AND it does not contain the tracking annotation/label.

Alternative:

• Implement this as a UI user preference (settings/appearance) and it is the UI that filters these resources from the different views. 🤔

Note that this has no improvements on performance, but it will improve the UX.