Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1110

Support servicebinding.io/v1beta1 resources

XMLWordPrintable

    • AppSvc Sprint 220, AppSvc Sprint 221, AppSvc Sprint 222

      Owner: Architect:

      <Architect is responsible for completing this section to define the details of the story>

      Story (Required)

      As an OpenShift user, I would like to be able to use servicebinding.io/v1beta1 resources in accordance with the specification.

      Background (Required)

      The specification has bumped resource versions from v1alpha3 to v1beta1 as a part of the 1.0 specification effort.

      Out of scope

      Don't remove support for v1alpha3 resources - we need to go through deprecation first.

      In Scope

      Allowing admission of v1beta1 resources and deprecating v1alpha3 resources.

      Approach(Required)

      There's not any semantic difference between the v1alpha3 and v1beta1 resources, so we should be able to accept them as-is.

      Acceptance Criteria

      • SBO should accept v1beta1 resources without throwing errors.
      • SBO should warn on applying v1alpha3 resource, stating their deprecated nature.
      • Update Test cases to use v1beta1
      • Add a few scenarios for depreciation warning.

      ...

      INVEST Checklist

      Dependencies identified
      Blockers noted and expected delivery timelines set
      Design is implementable
      Acceptance criteria agreed upon
      Story estimated

      Legend

      Unknown
      Verified
      Unsatisfied

            ansadler@redhat.com Andy Sadler
            ansadler@redhat.com Andy Sadler
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: