Andrea Morando

> ```yaml > apiVersion: argorpoj.io/v1alpha1 > ``` apiVersion: argorpoj.io/v1alpha1 Note the typo, "argorpoj", I noticed only after updating and recreated the crds a lot of times :-)

sorry, the example in https://github.com/argoproj/argo-helm/issues/840#issuecomment-1222787247

Make sure `curl -L https://github.com/argoproj-labs/argocd-vault-plugin/releases/download/v$(AVP_VERSION)/argocd-vault-plugin_$(AVP_VERSION)_linux_amd64` is correctly resolved. In my a case a text "Not Found" instead of the binary caused this error message. Replicing with https://github.com/argoproj-labs/argocd-vault-plugin/releases/download/v1.17.0/argocd-vault-plugin_1.17.0_linux_amd64 worked.

Could be nice to have all resources configurable.

In my case the cluster dns was not resolving the **cluster.local** domain at all, the solution was to add also the clusterDomain. The installation was a k3s Cluster provisioned via...

Same issue. Uninstall, crd, operator **drop namespace ( with associated secrets )** and reinstall solved for me cert-manager-v1.19.1 bottlerocket-update-operator-1.6.0 bottlerocket-shadow-1.0.0