[BUG] Unstable e2e test cases when running in parallel on Kubernetes 1.30

[ABNER-1]

What happened:

  [kruise.io] PodProbeMarker with tcpCheck functionality
  /home/runner/work/kruise/kruise/test/e2e/framework/framework.go:315
    pod probe marker tcpCheck test [It]

[apps] InplaceVPA
/home/runner/work/kruise/kruise/test/e2e/apps/framework.go:24
  [kruise.io] CloneSet Updating with inplace resource
  /home/runner/work/kruise/kruise/test/e2e/framework/framework.go:315
    in-place update resource and env from label [It]
    /home/runner/work/kruise/kruise/test/e2e/apps/inplace_vpa.go:618

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kruise version:
• Kubernetes version (use kubectl version):
• Install details (e.g. helm install args):
• Others:

[ABNER-1]

Recently, Kruise enabled parallel execution in the e2e workflow for Kubernetes 1.30, but some test cases frequently fail.

Therefore, I created an issue to track these failures.
Any subsequent test cases that frequently fail will be consolidated in this issue.
Anyone interested in these issues is encouraged to contribute to improving the stability of these e2e test cases.

Once stability is achieved over a period of time, we plan to enable the parallel execution switch in the e2e tests for all versions of Kubernetes.

[ABNER-1]

another case:
resize policy [{"resourceName":"cpu","restartPolicy":"RestartContainer"}]
in-place update two container image, resource and env from metadata with priorities