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
Solved: knative function deployed via ArgoCD errors out on next sync: admission webhook "validation.webhook.serving.knative.dev" denied the request
#15021
our cluster is being managed by ArgoCD. I could successfully deploy the contents of the knative tutorial via ArgoCD, i.e. I have a hello-Function and one for the cloudevents player.
Both functions are working, I can send events and receive them in the CloudEvents player.
But now ArgoCD is throwing errors on next sync, although the resources have not changed in git. I assume that the YAML inside the cluster contains more fields than the YAML in the tutorial, hence ArgoCD thinks it needs to do something.
The error message is:
admission webhook "validation.webhook.serving.knative.dev" denied the request: validation failed: volume with name "kne-bundle-volume" not mounted: spec.template.spec.volumes[0].name
So, for the next poor soul stumbling upon this, the solution is to use the (almost) complete YAML from inside the cluster and put this into the git repository. This contains the volume mount and is thus not being rejected by the admission webhook.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
our cluster is being managed by ArgoCD. I could successfully deploy the contents of the knative tutorial via ArgoCD, i.e. I have a hello-Function and one for the cloudevents player.
Both functions are working, I can send events and receive them in the CloudEvents player.
But now ArgoCD is throwing errors on next sync, although the resources have not changed in git. I assume that the YAML inside the cluster contains more fields than the YAML in the tutorial, hence ArgoCD thinks it needs to do something.
The error message is:
So, for the next poor soul stumbling upon this, the solution is to use the (almost) complete YAML from inside the cluster and put this into the git repository. This contains the volume mount and is thus not being rejected by the admission webhook.
This might be a good addition to the docs, but might not fit the getting-started tutorial (as this does not use ArgoCD).
Kind Regards
Johannes
Beta Was this translation helpful? Give feedback.
All reactions