Tekton upgrade to v0.56.2 is broken about pipeline HOT 7 CLOSED

@rashedkvm most likely that's the case.
This is a tricky problem to solve. I do not exactly remember on which issue we discussed it, but using kubectl apply to upgrade from one release to the other is not really guaranteed to work. The main reason is that kubectl apply does merge the existing object and the "new" ones (the new release yaml). This can lead to errors such as what you got, or things where the CRD(s) still have the v1alpha1 "element" on the cluster, even though it's gone from the release.yaml.

This is where things like the operaton or an helm chart are useful.

There is very little we can do from tektoncd/pipeline, at least from how we do our release, today…

from pipeline.

Indeed, using operator, or having some "manual" maintenance planning. Here, it is a simple fix, you just need to update the configmap (commenting that field), and re-applying.

from pipeline.

@vdemeester you can mark this issue resolved. In our case, we are using the carvel tools to manage the upgrade of Tekton between LTS versions. Thanks!

from pipeline.

Sounds good @rashedkvm 👍🏼

from pipeline.

Perhaps related to the change introduced in #6937

from pipeline.

Hi @vdemeester. What's your recommendation however for us to go forward?

from pipeline.

@rszumlakowski I believe the recommended path is to use https://github.com/tektoncd/operator

We can try to declare the upgrade steps using https://carvel.dev/kapp/docs/v0.60.x/apply-ordering/

from pipeline.