You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having an issue with getting ksops to work with ArgoCD. The error I'm seeing in ArgoCD is:
The Kubernetes API could not find viaduct.ai/ksops for requested resource [ resource name ]. Make sure the "ksops" CRD is installed on the destination cluster.
I am using viaductoss/ksops:v4.2.1 and followed the instructions to integrate with ArgoCD using the Helm chart modifications.
This seems like argo is trying to apply the generator yaml directly to kubernetes rather than kustomize using it to generate an actual secret which should then be applied.
Hi @johnl , thanks for looking into this. I have just included my kustomization content at the bottom of the original message. I was more or less following the examples given on the KSops github page.
Not to misguide what you're looking into, but I noticed that Bitnami has a different way of installing CRD's than the ArgoCD charts. It's possible I haven't installed those correctly. I think the KSops instructions are given using the ArgoCD helm chart not Bitnami. Unfortunately I wasn't able to test with the ArgoCD chart because it needs a later version of Kubernetes and kubectl.
I am having an issue with getting ksops to work with ArgoCD. The error I'm seeing in ArgoCD is:
The Kubernetes API could not find viaduct.ai/ksops for requested resource [ resource name ]. Make sure the "ksops" CRD is installed on the destination cluster.
I am using viaductoss/ksops:v4.2.1 and followed the instructions to integrate with ArgoCD using the Helm chart modifications.
I have the following in my argocd-cm:
When I exec into my argocd repo pod I see the files that need to be there:
It seems like /usr/local/bin is part of the path. Running kustomize version gives me:
(devel)
Running ksops in the pod shows this:
This is what my secret generator looks like:
Kustomization file:
Other information:
Let me know if you need any more information.
The text was updated successfully, but these errors were encountered: