Argocd 3.3.3 contains fix argoproj/argo-cd#26469 which changes the kubernetes version returned by argocd from major.minor to major.minor.patch. Kubechecks v2 running against argocd 3.3.3 causes the kubernetes version calculation in kubechecks to return a 4-part instead of 3-patch version number which is incorrect:
This might be fixed by simply updating the argocd client library in kubechecks as I think I saw that kubechecks uses an argocd client library to get the k8s version, however I am not sure if that would be backwards compatible with older argocd versions or if some kind of compatibility translation in the version number needs to be added to kubechecks.
Argocd 3.3.3 contains fix argoproj/argo-cd#26469 which changes the kubernetes version returned by argocd from
major.minortomajor.minor.patch. Kubechecks v2 running against argocd 3.3.3 causes the kubernetes version calculation in kubechecks to return a 4-part instead of 3-patch version number which is incorrect:This might be fixed by simply updating the argocd client library in kubechecks as I think I saw that kubechecks uses an argocd client library to get the k8s version, however I am not sure if that would be backwards compatible with older argocd versions or if some kind of compatibility translation in the version number needs to be added to kubechecks.