Error creating resources and running demo about pipelines-tutorial

[josequaresma]

I get similar error on OCP 4.3.0 and pipelines 0.10.7:
error: unable to recognize "01_pipeline/01_apply_manifest_task.yaml": no matches for kind "Task" in version "tekton.dev/v1beta1"

[DonSchenck]

I'm getting this as well.

[piyush-garg]

If you want to use the operator v0.10.7 then please use release-0.9 branch of the tutorial or if you want to use current master or release-tech-preview-1 of tutorial then please use operator 0.11.x

[Keyvan-rh]

Is it possible to use the 1.0.1 which is RedHat GAed and not the community one?

[piyush-garg]

@Keyvan-rh Yaa you can use that one also, it has v1beta1 resources.

[tux1980]

Hi, I'm getting this either:
error: unable to recognize "03_trigger.yaml": no matches for kind "Trigger" in version "triggers.tekton.dev/v1alpha1"

[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.