some argocd e2e testcases failed because of "violates PodSecurity", how do you deal with it

[chao-yu-wq]

When I run argocd testcase on master or tag2.14.15, tag3.0.6, I alway hit the issues like "violates PodSecurity" as the k8s cluster is relatively new version 1.32 or 1.33.

I also know the argocd community run the argocd e2e test cases on latest K8S versions, so how do you skip "violates PodSecurity".

I can make some walk-around coding such as "Run("", "kubectl", "label", "ns", DeploymentNamespace(), "pod-security.kubernetes.io/enforce=privileged", "--overwrite")" to skip this kind of issue. But I have to update some code file such as "test/e2e/fixture/fixture.go".

So I am wondering how do you deal with it?