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

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

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 16 (2 by maintainers)

Most upvoted comments

I figured out my issue. Somewhere in upgrading ArgoCD switched from using a Deployment to using a StateFul set and upgrading via ArgoCD didn’t delete the old Deployment, so it ended up abandoned. So we had a 1.7.8 application controller and a 2.2.3 application controller running at the same time, fighting with each other. If Google bring you here try running the following.

kubectl get pods

Mine looked like this. There should only be one “application-controller”. 5c5488c47d-vgrkj is the old one that shouldn’t be there

$ k get pods
NAME                                                 READY   STATUS    RESTARTS   AGE
argocd-application-controller-0                      1/1     Running   0          7d2h
argocd-application-controller-5c5488c47d-vgrkj       1/1     Running   0          10d
argocd-dex-server-6fb7bd4d7-sgdjf                    1/1     Running   0          7d2h
argocd-redis-584f4df7d7-7hfdq                        1/1     Running   0          7d2h
argocd-repo-server-55d56dd69f-fxqjt                  1/1     Running   1          7d2h
argocd-server-f7b574bc4-g7zp4                        1/1     Running   0          7d2h

+15

jdmulloy on Feb 7, 2022

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 on Nov 27, 2020

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

tsde on Dec 10, 2020

thank you for updating the issue @Prototik !

alexmt on Oct 14, 2020

That’s fixed by 3ae1d13dfd541c34a2b970b7a6d8f32f2369d31a

Prototik on Oct 14, 2020