search

openshift / pipelines-tutorial

A step-by-step tutorial showing OpenShift Pipelines
Apache License 2.0
298 stars 621 forks source link

no matches for kind "Trigger" in version "triggers.tekton.dev/v1alpha1" with OCP 4.5.11 #107

Closed tux1980 closed 3 years ago

tux1980 commented 3 years ago

Morning,

my second Issue I did recognize after creating the trigger-template and the trigger-binding (which have been successful). Always with trying apply the "trigger" yaml file I get the follow error message:

"error: unable to recognize "03_trigger.yaml": no matches for kind "Trigger" in version "triggers.tekton.dev/v1alpha1""

YAML Content:

apiVersion: triggers.tekton.dev/v1alpha1 kind: Trigger metadata: name: vote-trigger spec: serviceAccountName: pipeline bindings:

I did try out a couple of hints and clues in the GIT articles, without being successful yet.

TA Wolfgang

fleason commented 3 years ago

I am getting same error on IBM ROKS:

[@localhost dev]$ oc version
Client Version: 4.5.0-202005291417-9933eb9
Server Version: 4.5.15
Kubernetes Version: v1.18.3+2fbd7c7
[@localhost dev]$ tkn version
Client version: 0.11.0
Pipeline version: v0.17.3
Triggers version: v0.6.1
[@localhost dev]$ oc create -f pipelines-tutorial/03_triggers/03_trigger.yaml 
error: unable to recognize "pipelines-tutorial/03_triggers/03_trigger.yaml": no matches for kind "Trigger" in version "triggers.tekton.dev/v1alpha1"

I have opened a Case with IBM Support. CS2042101

fleason commented 3 years ago

I received help from @chaseo on #armada-users. He provided the following patch: kubectl apply --filename https://storage.googleapis.com/tekton-releases/triggers/latest/release.yaml This cleared the problem and the Trigger was created.

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/pipelines-tutorial/issues/107#issuecomment-816646401): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.