tektoncd/operator

On install, conflicting components are created

corinz opened this issue · 5 comments

corinz commented

When installing the crds, and operator via release.yaml with the instructions found here, the operator launches some Tekton components.

After step 1 is completed, the instructions advise the creation of a TektonConfig, which, after applied, deletes the original components, and replaces with them with new components (pods).

If the intent is to use release.yaml with a TektonConfig, the release.yaml should not create any components by default.

I propose that release.yaml only create the CRDs and operator, without installing any components by default.

Proposal: change AUTOINSTALL_COMPONENTS env var set in the tekton-operator/tekton-config-defaults configmap be set to false by default to prevent this collision/conflict.

piyush-garg commented

Thanks @corinz for reporting

Seems like something wrong with the value here. We need to fix the default value or need to update the doc

  • 👍1
divyansh42 commented

/assign

divyansh42 commented

As per the Slack conversation, we will be doing the documentation update to reflect the current behavior.
We are not making any changes in the present behavior as it might break/confuse the existing user's flow.

divyansh42 commented

Hi @corinz
I am trying to reproduce the issue but I don't see pods getting re-created after applying the config. Could you check again?
I just did the two steps mentioned here

divyansh42 commented

However, I agree with your point that the first step also installs the Tekton components