Optimizing CR processing after Kubernetes CRD controller restart

[lingdie]

I'm working with a Kubernetes Custom Resource Definition (CRD) controller. I've noticed that when the controller restarts, it attempts to reconcile all existing Custom Resources (CRs). This process causes a delay in processing newly created CRs.

My questions are:

1. What are the best practices to mitigate this delay in processing new CRs after a controller restart?

2. Does the controller-runtime library provide any built-in mechanisms to implement a priority queue or similar functionality to prioritize the processing of new CRs?

3. If controller-runtime doesn't offer such functionality, what are some effective ways to implement a priority system within the reconciliation loop?

4. Are there any performance considerations or potential drawbacks to implementing a priority system in a CRD controller?

I'm particularly interested in solutions that can be implemented using Go and the controller-runtime library. Any insights, code examples, or best practices would be greatly appreciated.

[sbueringer]

Great timing 😃. I would recommend trying #2374 once v0.20 is out

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale