Hey everyone! I'm facing a couple of issues related to KEDA across my two clusters that I could use some help with. First, in one of my clusters, KEDA seems to have been installed using Helm, but when I check the releases in Lens, I can't find KEDA listed there. However, I can see the KEDA deployments and pods running. This deployment is managed through Argo, and when I update the target revision in Argo, the deployments are updated accordingly, but the Helm release still doesn't show in Lens. Can anyone clarify how this might be happening?
Secondly, in another cluster, I'm using KEDA version 2.16.1. This version is mentioned in the KEDA GitHub repository and it matches what I see in Argo. However, when I check in Lens, it shows the version as 2.8.2, which is confusing. Why is there a version mismatch? Any insights would be appreciated!
1 Answer
So, it looks like Argo doesn't actually deploy using Helm directly. Instead, it utilizes 'helm template' to convert Helm charts into Kubernetes manifests and directly applies those. That's why you’re able to see the deployments and pods without seeing them listed as a Helm release in Lens. Helm tracks releases using secrets, and since Argo isn't creating those, Lens can't find them in its release tracking.
As for your version issue, it’s possible there’s a confusion with how KEDA was installed in that cluster or perhaps an older version was cached. You might want to double-check the installation method or any existing Helm releases that might influence the version output.
Thanks for clarifying that! I was indeed confused about how Argo and Helm interact. I’ll look into the installation method for the version issue.