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

Define ClusterEnvironment API

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • Primaza 0.1
    • Primaza 0.1
    • Service Binding
    • AppSvc Sprint 230

      Owner: Architect:

      David Peraza

      Story (Required)

      As an OpenShift Developer, I would like to be able to create ClusterEnvironment resources in Primaza namespaces so that primaza can read service data and push claim data to the cluster.

      Background (Required)

      We need to define the ClusterEnvironment API defined in the primaza architecture document. See epic for arch document link.

      Glossary

      See glossary in architecture document

      Out of scope

      Pushing any agents/controllers to the clusters

      In Scope

      Focus on ApplicationAndService cluster types.
      Make sure the Primaza cluster itself can be added as a cluster.

      Approach(Required)

      Define the ClusterEnvironment CRD. Controller should validate if cluster is online or offline.

      • Check if cluster is online if we can connect to it
      • Cluster is offline if there is no connectivity, there should be an error message describing the issue

      Demo requirements(Required)

      A good demo will show 2 ClusterEnvironment resources, one with online status, and one with offline status

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      • Development
        ClusterEnvironment CRD is defined
        ClusterEnvironmentRegistrar controller is developed
      • QE
        There are test cases for online, and offline clusters.
      • Docs
        There is a page in our docs dedicated to explaining what a ClusterEnvironment is including the different states it could be in and the error conditions
        Update architecture document with any changes while implementing
        There is a link in our main readme to the ClusterEnvironment page

      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

              rh-ee-filario Francesco Ilario
              dperaza@redhat.com David Peraza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: