README suggests try.openshift.com, but users cannot install operators about pipelines-tutorial

[nikhil-thomas]

hi, at present OpenShift Pipelines Operator is not supported on try.openshift.com. Let me try to help you with the 2nd question.

or some other clues we could give users in the README?

@siamaksade @vdemeester

@ktdreyer feel free to reach us on tektoncd-pipeline-devchannel on coreos slack. 🧑‍💻

[ktdreyer]

Thanks.

Should we remove all try.openshift.com references in this tutorial, then?

What would you recommend instead?

[vdemeester]

Note that it doesn't work with the "Developer sandbox" (first box) but it should work with the other options (Managed Services and Self-Managed). We may want to add in the README that it doesn't run on "Developer sandbox" (yet).

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

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