[BUG] Operator reports "Ready: True" when TektonConfig reports "Error"

[adambkaplan]

Is there an existing issue for this?

• I have searched the existing issues

Kubernetes Version

v1.25 or higher

Shipwright Version

v0.12.0 (and earlier)

Current Behavior

When the TektonConfig object (existing, or created by the Shipwright operator) reports its status as Error/not available, the ShipwrightBuild object only reports its status condition as "Ready: True".

Expected Behavior

ShipwrightBuild should either report a status condition of "Ready: False", or report a new status condition like "Available" which is used to convey the overall health of the system.

Steps To Reproduce

1. Deploy OLM on Kubernetes 1.25 or higher (ex - with KinD)
2. Deploy the Shipwright Operator using the operatorhub.io catalog - ensure it uses Tekton Operator v0.61 or lower
3. Create a ShipwrightBuild instance

Anything else?

Related to tektoncd/operator#1493 - the Tekton Operator in operatorhub is currently obsolete and breaks on k8s 1.25 or higher.

[SaschaSchwarze0]

@adambkaplan is this something blocking that we should address for v0.13 ?

[adambkaplan]

I would not consider this blocking for v0.13.0

[adambkaplan]

From backlog refinement: We should wait until #139 is addressed before taking this on. Upgrading operator-sdk will involve a significant refactor of the operator code itself.

[adambkaplan]

From backlog refinement: We should wait until #139 is addressed before taking this on. Upgrading operator-sdk will involve a significant refactor of the operator code itself.

Whew...one year later and we still have operator-sdk refactor pain. This bug is no longer blocked - we have a PR that is in good shape and should land early in the v0.17 lifecycle.