Introduce a new operator profile none

[ezh]

Feature request

The current installation profiles for Tekton include all, basic, and lite, which provide a predefined set of components to be installed on the cluster. However, there is no option for users who want to install specific components selectively without being restricted to the predefined sets.

I propose the introduction of a 'none' profile that allows users to install no components by default, giving them the flexibility to add specific components as needed.

Use case

Tekton operator is very limited in Tekton pipeline installation and sometimes points to outdated versions.
I want to install Tekton pipelines with custom patches for CRDs and other kubernetes resources.
At the same time, it would be great to use the operator for pruning, addons, etc.

[vdemeester]

Hey @ezh. So in theory, you can just remove the TektonConfig CRD and manage the rest on your own (aka using TektonPipeline and other sub-objects).

Tekton operator is very limited in Tekton pipeline installation and sometimes points to outdated versions.
I want to install Tekton pipelines with custom patches for CRDs and other kubernetes resources.
At the same time, it would be great to use the operator for pruning, addons, etc.

I wonder if this would not be a reason to extract some of the operator's feature to their own tektoncd project — that we would package in the operator — but that could be installable on their own, independently of the operator.

[AlanGreene]

This request sounds related to / very similar to #1474 which proposes removing the concept of profiles entirely and just allowing users to enable individual components as needed.