fix(e2e): Fixed sporadic end-to-end (e2e) failures caused by slow pod…

[Syspretor]

… processing.

Ⅰ. Motivation

Ⅱ. Modifications

Summary

Fix sporadic e2e test failures and enhance diagnostic capabilities.

Problems Fixed

1. E2E case ConfigMap Not Found

Root Cause: The ensureDiscoveryConfigMode was called after constructAndUpdateRoleStatuses, which populates rbg.Status.RoleStatuses. This caused shouldUseLegacyDiscoveryConfig to incorrectly detect new RBGs as legacy ones, resulting in ConfigMap not being created before workload creation.

Fix: Reorder reconcile steps - move discovery config mode initialization and ConfigMap creation before status construction.

2. Deployment Status Overwritten

Root Cause: When pod_controller calls setRestartCondition, it patches the entire status including stale RoleStatuses from memory, overwriting the latest values updated by rbg_controller (both use the same FieldManager="rbg").

Fix: Create toRBGApplyConfigurationForConditionsOnly to patch only conditions without touching RoleStatuses.

3. Image Pull Timeout in CI

Fix: Pre-load e2e test images into Kind cluster before running tests.

Diagnostic Enhancements

• Add comprehensive debug info output for all test cases (RBG status, workload status, pod conditions)
• Only dump debug info on test failure
• Query and display Pod events for not-ready pods to help diagnose root causes
• Increase test timeout from 90s to 150s

Ⅲ. Does this pull request fix one issue?

fixes #XXXX

Ⅳ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.

Ⅴ. Describe how to verify it

VI. Special notes for reviews

Checklist

• Format your code make fmt.
• Add unit tests or integration tests.
• Update the documentation related to the change.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[cheyang]

/lgtm
/approve

[cheyang]

/lgtm
/approve