triggers: event listener error unsupported protocol scheme

Expected Behavior

Event listener should work with github webhook.

Actual Behavior

{"severity":"error","timestamp":"2022-12-13T10:31:20.746Z","logger":"eventlistener","caller":"sink/sink.go:412","message":"Post \"\": unsupported protocol scheme \"\"","eventlistener":"github-token","namespace":"tekton-pipelines","/triggers-eventid":"b2b5820d-c466-42bb-83f2-69a3a1572f8a","eventlistenerUID":"7eef4c33-d2c9-4d2b-b528-826112b81596","/triggers-eventid":"b2b5820d-c466-42bb-83f2-69a3a1572f8a","/trigger":"springboot"}

Steps to Reproduce the Problem

  1. When github event is received by el it gives error unsupported protocol scheme

Additional Info

  • Kubernetes version: 1.24

    Output of kubectl version:

    Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:28:30Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"darwin/arm64"}
    

Kustomize Version: v4.5.7 Server Version: version.Info{Major:“1”, Minor:“24+”, GitVersion:“v1.24.7-eks-fb459a0”, GitCommit:“c240013134c03a740781ffa1436ba2688b50b494”, GitTreeState:“clean”, BuildDate:“2022-10-24T20:36:26Z”, GoVersion:“go1.18.7”, Compiler:“gc”, Platform:“linux/amd64”}


- Tekton Pipeline version:

**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**
Client version: 0.28.0
Pipeline version: v0.42.0
Triggers version: v0.22.0
Dashboard version: v0.30.0

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (7 by maintainers)

Commits related to this issue

Most upvoted comments

I’m seeing the same error when using triggerGroups on OpenShift 4.11 (Kubernetes 1.24.6), using Tekton via the Red Hat OpenShift Pipelines operator (which provides Triggers v0.22.0).

If anyone else is hitting this issue, a workaround that fixed it for me was simply to provide the kind in the interceptors. So instead of this:

  triggerGroups:
    - name: app-engine-triggers
      interceptors:
        - ref:
            name: "github"
          params:
            - name: "secretRef"

Include kind: ClusterInterceptor in the ref:

...
  triggerGroups:
    - name: app-engine-triggers
      interceptors:
        - ref:
            name: "github"
            kind: ClusterInterceptor    # <--- add this
          params:
            - name: "secretRef"

It may already be fixed in the most recent version of Triggers, or will be shortly, but this workaround shouldn’t later cause problems if you apply it. 🤞