Help us shape the future of Argo CD 3.0!

As you have probably read, we are working on a new major Argo CD release, and would love for your feedback to make this release even better!
This is your opportunity to affect Argo CD 3.0!

Help us make Argo CD more performant out of the box by informing us about:

1. Widely used Kubernetes resource fields, that are known to have high churn, meaning, K8s resource fields, which should be ignored by Argo CD with ignoreResourceUpdate.
   Please add more such resources that you have encountered during your every day work with Argo CD (for example, status field) to this list.
2. Kubernetes internal resources that most of you never directly create. They can clutter the UI and decrease Argo performance due to high churn.
   Please add more such resources that you have encountered during your every day work with Argo CD (for example, Endpoints and EndpointSlice resources) to this list.

Help us make Argo CD more secure out of the box by informing us about:

1. How wide is the adoption of project scoped clusters and your methodologies of sharing clusters between AppProjects. Please share your feedback as a vote here.

Help us promote the maturity of some Alpha and Beta features:

We are considering the maturity promotion of some of those Argo CD features (Alpha -> Beta, Beta -> Stable).
Please add your input on this list of issues for the features, as a vote:

1. If you have successfully adopted the feature, please vote “thumbs-up” on the issue.
2. If you are familiar with any blockers for promoting the feature, please vote “thumbs-down” on the issue and comment with more details.

Thank you for helping us shape this release!