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

Determine minimum version of kubernetes we wish to support

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Undefined
    • Primaza 0.1
    • None
    • None
    • None
    • False
    • None
    • False

    Description

      Owner: Architect:

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

      Story (Required)

      We should determine the minimum version of kubernetes we wish to support.

      Background (Required)

      In the lead up to more stable releases of primaza, we should start thinking about which versions of k8s we want to support (and, more importantly, which versions we don't want to support).

      Glossary

      <List of new terms and definition used in this story>

      Out of scope

      <Defines what is not included in this story>

      In Scope

      <Defines what is included in this story>

      Approach(Required)

      Determine the minimum version primaza still works on, and use that to inform our decision. We can probably go as far back as OpenShift 4.8 (k8s 1.21). With this information, we can make a better judgement on what we should and shouldn't support.

      Demo requirements(Required)

      _<Description of demo which would show the value of this story. Any demo
      should also be included as part of the acceptance criteria.>_

      Dependencies

      _<Describes what this story depends on. Dependent Stories and EPICs should
      be linked to the story.>_

      Edge Case

      _<Describe edge cases to consider when implementing the story and defining
      tests>_

      Acceptance Criteria

      _<Provides a required and minimum list of acceptance tests for this story.
      More is expected as the engineer implements this story>_

      Development:
      Documentation: Yes (which versions we do and don't support)

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      v

      Legend

      Unknown

      Verified

      Unsatisfied

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated: