You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Source to Image and Builder Automation (Tekton)" row is misleading. It should be split into two distinct rows. Source to Image (S2I) is a different feature than OpenShift Pipelines (Tekton). The first is available from the base platform, web console and the oc CLI but the second requires installing an add-on operator and using the custom resources, CLI, and web console extensions from that operator. While OpenShift Pipelines can use S2I it can also ignore it completely and S2I does not require Pipelines.
The text was updated successfully, but these errors were encountered:
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.
openshift-cibot
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jan 6, 2023
Which section(s) is the issue in?
Table 2
What needs fixing?
The "Source to Image and Builder Automation (Tekton)" row is misleading. It should be split into two distinct rows. Source to Image (S2I) is a different feature than OpenShift Pipelines (Tekton). The first is available from the base platform, web console and the oc CLI but the second requires installing an add-on operator and using the custom resources, CLI, and web console extensions from that operator. While OpenShift Pipelines can use S2I it can also ignore it completely and S2I does not require Pipelines.
The text was updated successfully, but these errors were encountered: