feat: ignore endpointslice modified events, and add tests

[fungiboletus]

This is related to a comment stating that endpointslice should be ignored.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.95%. Comparing base (98ccd3d) to head (c89a5a1).
Report is 47 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #469      +/-   ##
==========================================
+ Coverage   55.46%   55.95%   +0.48%     
==========================================
  Files          41       41              
  Lines        4504     4504              
==========================================
+ Hits         2498     2520      +22     
+ Misses       1813     1794      -19     
+ Partials      193      190       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
2 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sidewinder12s]

This would be useful, we have a lot of DaemonSets with services that are causing constant reconciliations due to constant cluster scaling.

[aaemula]

This change is awesome.
So we don't have to manually configure the resource.exclusions.

[aaemula]

@crenshaw-dev @alexmt @jessesuen PTAL

[diranged]

What needs to be done to get this over the hump? This has a serious load impact for us (argoproj/argo-cd#15594 (comment)).

[agaudreault]

I don't think we should hardcode these resources to be ignored by default. It is already possible to configure them via resource.exclusions. Perhaps It is time to provide a default exclusion configuration that includes these resources?

This would allow users the be able to configure the behavior they want, while providing sensible default.

[fungiboletus]

Is there a scenario where you don't want EndpointSlice to be ignored? I saw the code was ready to add more ignored ressources so I just added it there.

I think it's fine to have default ignored ressources in resource.exclusions instead. I wouldn't mind if someone else feels like implementing it :D

[agaudreault]

@fungiboletus we do have them in the UI because they contain useful networking information to identify and debug some network problems.

I created an issue for the 3.0 version to change the default settings argoproj/argo-cd#20013 :)