unable to recognize "/yaml Path": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1

[iamdebu]

Bug report

unable to recognize "/yaml path": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1"

[Description of the bug]
We are setting up an AKS cluster and for service mesh we are using ISTIO. We have a set of scripts to configure ISTIO. The scripts were working correctly till 1.19 version of Kubernetes. Now with the new AKS cluster the old (Kubernetes 1.19) version is not available. So, we had to deploy the AKS cluster with 1.21.2 version. With the new version the old set of scripts are not working. Below are the problems we are facing:

unable to recognize "/yaml path": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1"
unable to recognize “/yaml path ": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1"
unable to recognize "/yaml path ": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1"
unable to recognize "/yaml path ": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1"

We checked the compatibility and found that it should be working fine. Please find the link for the details:
https://istio.io/latest/docs/releases/supported-releases/

We tried below solution, but it didn’t work:
#783
Expected behavior: [What you expected to happen]
ISTIO should be setup without any issue
Actual behavior: [What actually happened]
Throwing the below issue:
unable to recognize "/yaml path": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1beta1"
Version(s) affected: [run krane version]
We are using ISTIO V 1.10.2 and Kubernetes V 1.21.2, Kubectl Version 1.20

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Feature request

• If the maintainers agree with the feature as described here, I intend to submit a Pull Request myself.¹

Proposal: [provide details on the behaviour you'd like to see and why it would be useful]

¹ _{This is the quickest way to get a new feature! We reserve the right to close feature requests, even ones we like, if the proposer does not intend to contribute to the feature and it doesn't fit in our current roadmap.}