fix occasional restarts of kruise controller manager

[PersistentJZH]

Ⅰ. Describe what this PR does

fix occasional restarts of kruise controller manager

root cause: The CRD installation was completed later than the CRD index registration time during the start of kruise-controller-manager.

Ⅱ. Does this pull request fix one issue?

Fix: #2380

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

[kruise-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign furykerry for approval by writing /assign @furykerry in a comment. For more information see:The Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Copilot]

Pull request overview

This PR addresses intermittent kruise-controller-manager restarts during startup by preventing field index registration for ImagePullJob (v1alpha1) until the corresponding CRD/version is discoverable, avoiding “no matches for kind” errors when CRDs are established slightly later than the controller starts.

Changes:

• Guard ImagePullJob (apps.kruise.io/v1alpha1) ownerReference field index registration behind utildiscovery.DiscoverObject.
• Align v1alpha1 ImagePullJob ownerRef index registration behavior with other CRD-gated index registrations already present in RegisterFieldIndexes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

DiscoverObject(&appsv1alpha1.ImagePullJob{}) is now called here and again later in RegisterFieldIndexes (for the isActive index). Because DiscoverObject can retry with exponential backoff, calling it multiple times for the same GVK can noticeably slow startup in CRD-not-ready scenarios and can also lead to inconsistent registration (e.g., ownerRef index registered but isActive skipped, or vice versa). Consider computing the discovery result once (e.g., hasImagePullJobV1Alpha1 := utildiscovery.DiscoverObject(...)) and reusing it for all ImagePullJob v1alpha1 index registrations (and similarly for v1beta1).

[codecov]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.68%. Comparing base (bba2621) to head (669dbb7).

Files with missing lines	Patch %	Lines
pkg/util/fieldindex/register.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2382      +/-   ##
==========================================
+ Coverage   48.66%   48.68%   +0.01%     
==========================================
  Files         324      324              
  Lines       27920    27921       +1     
==========================================
+ Hits        13587    13592       +5     
+ Misses      12794    12791       -3     
+ Partials     1539     1538       -1     

Flag	Coverage Δ
unittests	48.68% <0.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[PersistentJZH]

/cc @zmberg @furykerry