[TektonConfig] Remove the concept of "profiles" and instead specify components individually

[tculp]

Feature request

The "profile" concept seems unhelpful, restricting, and obtuse. Instead, why not just have the config specify the exact components to install? Or add an enabled field to the individual pipeline, dashboard, etc. sections.

Use cases

• I want to install only tekton-pipelines and tekton-dashboard, but I don't want to install tekton-triggers. No profile gets me that combination of components, so profiles aren't usefult to me.

• I want to install tekton-dashboard on an OpenShift install, but no profile allows for that.

General issues

• As a new user, it's unexpected that the components installed with the all profile changes based on the flavor of Kubernetes. See [Question] Should we make all components common for all platforms #400. Also, it does not in fact install all components, so the term is misleading

• As new components are added to Tekton Operator, it'll become harder to add new profiles and combinations, especially in a backwards-compatible way

• lite and basic are very similar terms semantically, and convey no information about which components they each install without specifically looking at the documentation at https://tekton.dev/docs/operator/tektonconfig/#profile. A simple list of components or set of enabled flags would be clearer

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tculp]

/remove-lifecycle stale Still an issue

[vdemeester]

/lifecycle frozen