Argo-cd: ComparsionError when using networking.k8s.io/v1 Ingress

[Prototik]

Describe the bug

I tried to manage project that defined Ingress from networking.k8s.io/v1 api group (k8s 1.19).
Initial sync is ok, but I cannot sync any more times because of following error:

ComparisonError
failed to convert *unstructured.Unstructured to *v1beta1.Ingress: no kind "Ingress" is registered for version "networking.k8s.io/v1" in scheme "pkg/runtime/scheme.go:101"

To Reproduce
Just create any networking.k8s.io/v1 Ingress within 1.19 cluster

Expected behavior
ArgoCD works with v1 Ingress

Version
1.7.5

[alexmt]

Probably fixed by https://github.com/argoproj/gitops-engine/pull/139

[Prototik]

That's fixed by 3ae1d13dfd541c34a2b970b7a6d8f32f2369d31a

[alexmt]

thank you for updating the issue @Prototik !

[kingdonb]

I still get comparisonerror, is this change in a release? (It seems by now it would be, there have been a couple of releases since Oct 14, but I can't find it mentioned in any release notes.)

This report is from argocd:v1.7.10:

$ ka get deploy -oyaml|grep image:|grep -v f:image
          image: argoproj/argocd:v1.7.10
          image: quay.io/dexidp/dex:v2.22.0
          image: argoproj/argocd:v1.7.10
          image: redis:5.0.10-alpine
          image: argoproj/argocd:v1.7.10
          image: argoproj/argocd:v1.7.10

time="2020-11-23T17:59:22Z" level=info msg="Sync operation to 58472b1d5967b726e24ca8451b71d85d688a77e9 failed: ComparisonError: failed to convert *unstructured.Unstructured to *v1beta1.Ingress: no kind \"Ingress\" is registered for version \"networking.k8s.io/v1\" in scheme \"pkg/runtime/scheme.go:101\"" application=pa-dev dest-namespace=pa dest-server="https://kubernetes.default.svc" reason=OperationCompleted type=Warning

[jshin47]

I also still have the same issue after upgrading to the manifest from tag 1.7.0

[avdhoot]

@alexmt Even after updating argocd to 1.7.10 still facing the same issue.

[tsde]

@alexmt Same issue here as well on version 1.7.10. Maybe the fix is still not included in a release ?

[avdhoot]

As temp solution we are using argoproj/argocd:latest cc @tsde @jshin47

[tsde]

Thanks for the tip @avdhoot
I see that v1.8 is on its way and may include the fix. Though having confirmation here would be great ;)

[tsde]

@kingdonb @avdhoot @jshin47 I've just tested version 1.8.1 and this is now fixed (version 1.8.0 should be fine too)

[kingdonb]

Awesome, thanks 👍 confirmed on my end, I am in business now with
networking v1 ingresses and argo 1.8.1

tsde wrote:

@kingdonb https://github.com/kingdonb @avdhoot
https://github.com/avdhoot @jshin47 https://github.com/jshin47 I've
just tested version 1.8.1 and this is now fixed (version 1.8.0 should be
fine too)