SUMMARY The "helm deploy" command is failing for dcaemod in environments that are running newer versions of Kubernetes: no matches for kind "Ingress" in version "networking.k8s.io/v1beta1" The reason is that "Ingress" moved from beta to stable in k8s 1.19 and as of 1.22 the reference to the "networking.k8s.io/v1beta1" API is no longer recognized.  The correct reference is ""networking.k8s.io/v1" The API version is set in the common ingress template.  Apparently dcaemod is the only component that forces the use of an ingress in typical ONAP deployments (such as the gating runs), so it is the only component showing this problem. OS / ENVIRONMENT The problem can be seen in many gating runs, for instance in the Gitlab Azure 3 environment. OOM VERSION master CONFIGURATION gating configuration STEPS TO REPRODUCE oom gating run EXPECTED RESULTS The "helm deploy" command for dcaemod should succeed. ACTUAL RESULTS The "helm deploy" command fails with the error: Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"