What happened

When syncing Pods from a real cluster (Cluster A) to a kwok-based simulator cluster (Cluster B), the status of the Pods is not patched. This causes completed Pods (e.g., Succeeded or Failed) to remain in Running state in the simulator.

What you expected to happen

The kwok-based simulator cluster should reflect the actual status.phase of Pods from the source cluster, including terminal states like Succeeded or Failed.

How to reproduce it

1. Create a Pod in Cluster A.
2. Let it complete (Succeeded or Failed).
3. Sync it to Cluster B using the kube-scheduler-simulator.
4. Observe that in Cluster B, the Pod remains in Running state.

Anything else we need to know?

• The issue was discovered while using kwok as the target cluster for simulation.
• A fix for this has been proposed in PR Bugfix: sync pod /status correctly in kwok-based simulator cluster #434 .
• We may also need to handle status patching during updates (UpdateFunc) and not just creation.

/sig scheduling
/area simulator
/kind bug