Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-430

Use operator.tekton.dev/release label to detect Tekton version

XMLWordPrintable

    • Future Sustainability
    • 3
    • False
    • False
    • Sprint 224, Sprint 225, Sprint 226, Sprint 227, Sprint 228, Sprint 230, Pipeline Integrations #243
    • 7

      User Story

      As a cluster admin
      I want the Shipwright operator to detect the "upstream" version of Tekton deployed on the cluster
      So that Shipwright deploys the build controller with a supported version of Tekton.

      Acceptance Criteria

      • Shipwright operator reads the "upstream" label of Tekton's CRD resources
      • If the detected version of Tekton is supported, Shipwright is able to deploy Shipwright Builds
      • If the detected version of Tekton is not supported, Shipwright reports an error condition.

      Docs Impact

      None

      PX Impact

      None

      QE Impact

      None

      Notes

      Upstream issue: https://github.com/shipwright-io/operator/issues/61

      Simply fixing the issue is very fast. However we may want to use this as a refactoring opportunity. We don't have very strong e2e test coverage, we can improve the code quality here.

              jkhelil abdeljawed khelil
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: