Closed comtihon closed 11 months ago
Update: Looks like it is not an argocd issue, but helm. When I try to install helm package via helm I get the same error:
helm install name name-0.2.108.tgz -f values.yaml
Error: INSTALLATION FAILED: 1 error occurred:
* admission webhook "webhook.argo-events.argoproj.io" denied the request: template nam-trigger is invalid, unknown operation type create
looks like the reason was in the incorrect yaml. I compared example with my code line by line and found it
I package my workflows (sensor + event source) in helm package during ci/cd. In the argocd manifest I specified this package to be installed. I found it convenient as we have multiple workflows repo and a single infra repo where we mention it together with other apps. But the problem I faced is - when it tries to install it via ArgoCD - it installs event source without any problem, but it fails to install the sensor:
admission webhook "webhook.argo-events.argoproj.io" denied the request: template pubsub-workflow-trigger is invalid, unknown operation type create
If I run it manually viakubectl apply -n argo-events -f sensor.yaml
it says created. And after it the sensor is even visible by ArgoCD and marked as healthy.Checklist:
argocd version
.Describe the bug
ArgoCD can't install argo-event's sensor, although the same sensor (taken from argo examples) can be installed using
kubectl
command.To Reproduce
Expected behavior sensor installed via argo cd
Screenshots source:
sensor:
manifest:
Version
Logs