The admissionregistration.k8s.io/v1beta1 API version of MutatingWebhookConfiguration is no longer served as of v1.22.

Current EKS version：1.21
Purpose: Upgrade version to 1.22
EKS upgrade insights shows that there are deprecated api versions：

Check cluster：
`kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io -A`

Check details：
`kubectl get MutatingWebhookConfiguration.v1beta1.admissionregistration.k8s.io "0500-amazon-eks-fargate-mutation.amazonaws.com" -o yaml | grep apiVersion`
`kubectl get MutatingWebhookConfiguration.v1.admissionregistration.k8s.io "0500-amazon-eks-fargate-mutation.amazonaws.com" -o yaml | grep apiVersion`

The difference between the two: **v1beta1 & v1**

Question：
1、In the second picture, why does the first row show v1, but the second column shows v1beta1?
2、If I upgrade to v1.22, will v1beta1 in the first picture be automatically updated to v1? In the same way, will the second row in the second picture also be updated?

For "pod-identity-webhook", the phenomenon is the same as above.
`kubectl get MutatingWebhookConfiguration.v1beta1.admissionregistration.k8s.io "pod-identity-webhook" -o yaml | grep apiVersion`
`kubectl get MutatingWebhookConfiguration.v1.admissionregistration.k8s.io "pod-identity-webhook" -o yaml | grep apiVersion`

Guys, is there anything I need to do before upgrading?

Start by reviewing the reported kubectl queries for MutatingWebhookConfiguration objects and the admissionregistration.k8s.io/v1beta1 and v1 API versions. Reproduce the checks against the relevant EKS versions, then document the observed version differences, upgrade impact, and any required action for pod-identity-webhook and the Fargate mutation configuration.

Written by the indexing model from the issue text.