fix: inplace update failed due to virtual kubelet in PUB

[chengjoey]

Ⅰ. Describe what this PR does

fix inplace update failed due to inplace update on vk node
skip inPlaceUpdateState check when pod is running on vk node

Ⅱ. Does this pull request fix one issue?

fix #1262

Ⅲ. Describe how to verify it

inplace update on vk node

[sonatype-lift]

Sonatype Lift is retiring

Sonatype Lift will be retiring on Sep 12, 2023, with its analysis stopping on Aug 12, 2023. We understand that this news may come as a disappointment, and Sonatype is committed to helping you transition off it seamlessly. If you’d like to retain your data, please export your issues from the web console.
We are extremely grateful and thank you for your support over the years.

📖 Read about the impacts and timeline

[kruise-bot]

Welcome @chengjoey! It looks like this is your first PR to openkruise/kruise 🎉

[chengjoey]

/assign @zmberg @ftpilot

[kruise-bot]

@chengjoey: GitHub didn't allow me to assign the following users: ftpilot.

Note that only openkruise members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @zmberg @ftpilot

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[hantmac]

How about making var together?

var (
labelNodeTypeKey = "type"
virtualNodeType = "virtual-kubelet"

taintVirtualToFind = &corev1.Taint{
		Key:    "virtual-kubelet.io/provider",
		Effect: corev1.TaintEffectNoSchedule,
	}
)

[chengjoey]

done

[hantmac]

I think there is no need to check the taints on node, virtualNode label is enough?

[chengjoey]

done, removed the judgment of taint， virtualNode label in enough

[hantmac]

/LGTM

[kruise-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hantmac
Once this PR has been reviewed and has the lgtm label, please ask for approval from zmberg by writing /assign @zmberg 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.

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

[zmberg]

This situation is still a bit more complicated, you can't skip the vk node so easily, many of our internal scenarios vk can be upgraded in place

[zmberg]

/hold

[kruise-bot]

New changes are detected. LGTM label has been removed.

[chengjoey]

This situation is still a bit more complicated, you can't skip the vk node so easily, many of our internal scenarios vk can be upgraded in place

Thanks! @zmberg, I added a judgment, only the pod running on the virtual node and UpdateEnvFromMetadata is turned on will skip the check

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.