no matches for kind "Trigger" in version "triggers.tekton.dev/v1alpha1" with OCP 4.5.11 about pipelines-tutorial

[fleason]

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.

[fleason]

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

[openshift-bot]

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]

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]

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]

@openshift-bot: Closing this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.