-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Interceptor references without a kind
don't get a URL set for execution
#1499
Comments
I think #1492 is likely the same root problem. |
See tektoncd#1499 Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Due to tektoncd/triggers#1499, all our event listeners were failing. I've pushed an image of `eventlistenersink` built from https://github.com/abayer/triggers/tree/default-to-clusterinterceptor (just one commit on top of Triggers v0.22.0) that fixes this and configured the `tekton-triggers-controller` deployment to use that image (gcr.io/abayer-jclouds-test1/eventlistenersink-7ad1faa98cddbcb0c24990303b220bb8@sha256:6d7769173bec31635bc9994fa5ffa3ae40c493315bf4ae7cca5aff24d824a889) as its `-el-image` argument, which has gotten everything working again, but if we'd prefer to run vanilla v0.22.0, this PR adds an explicit `kind: ClusterInterceptor` to every interceptor reference I could find, which should have the same effect. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
cc @afrittoli @dibyom @savitaashture - this is what borked Dogfooding. =) |
Hi @abayer i see we have added default kind as And I have tried installing Triggers |
I'd suggest trying to install v0.21.0, create an |
Due to tektoncd/triggers#1499, all our event listeners were failing. I've pushed an image of `eventlistenersink` built from https://github.com/abayer/triggers/tree/default-to-clusterinterceptor (just one commit on top of Triggers v0.22.0) that fixes this and configured the `tekton-triggers-controller` deployment to use that image (gcr.io/abayer-jclouds-test1/eventlistenersink-7ad1faa98cddbcb0c24990303b220bb8@sha256:6d7769173bec31635bc9994fa5ffa3ae40c493315bf4ae7cca5aff24d824a889) as its `-el-image` argument, which has gotten everything working again, but if we'd prefer to run vanilla v0.22.0, this PR adds an explicit `kind: ClusterInterceptor` to every interceptor reference I could find, which should have the same effect. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Worth mentioning that we call |
...and I see that's called in the Ah! I think the problem is that we're using |
Fixes tektoncd#1499 While `Kind` is getting defaulted properly for interceptors in `EventListener.Spec.Triggers`, it also needs to be defaulted for interceptors in `EventListener.Spec.TriggerGroups`. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Fixes #1499 While `Kind` is getting defaulted properly for interceptors in `EventListener.Spec.Triggers`, it also needs to be defaulted for interceptors in `EventListener.Spec.TriggerGroups`. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Fixes tektoncd#1499 While `Kind` is getting defaulted properly for interceptors in `EventListener.Spec.Triggers`, it also needs to be defaulted for interceptors in `EventListener.Spec.TriggerGroups`. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Fixes #1499 While `Kind` is getting defaulted properly for interceptors in `EventListener.Spec.Triggers`, it also needs to be defaulted for interceptors in `EventListener.Spec.TriggerGroups`. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Expected Behavior
Interceptor references without a
kind
should default to being treated asClusterInterceptor
s and have their URL set appropriately on Triggers v0.22.0, which worked properly in v0.21.0 and earlier.Actual Behavior
On v0.22.0, interceptor references without a
kind
skip over the if block attriggers/pkg/sink/sink.go
Lines 510 to 539 in 8797cc0
url
set, causing errors to show up in the eventlistener logs like:Steps to Reproduce the Problem
EventListener
referencing an interceptor by name without specifying thekind
.Additional Info
This was encountered on Tekton's dogfooding cluster after upgrading to v0.22.0.
The text was updated successfully, but these errors were encountered: