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

Add Documentation for reconciling namespaces

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • Primaza 0.1
    • Service Binding
    • None
    • AppSvc Sprint 234, AppSvc Sprint 236, AppSvc Sprint 238, AppSvc Sprint 239, AppSvc Sprint 240

      Owner: Architect:

      Francesco Ilario

      Story (Required)

      Add documentation for reconciling namespaces as part of stories

      Application Namespaces

      1. Namespace Creation
        1. Push ServiceCatalog
        2. Push ServiceBindings
      2. Namespace Deletion
        1. Primaza's resource deletion

      Service Namespaces

      1. Namespace Creation
        1. Push ServiceClass
      2. Namespace deletion
        1. Primaza's resource deletion

      Background (Required)

      Add the documentation for Application/Service Namespaces lifecycle as implemented linked stories.

      Glossary

      See glossary in architecture document

      Out of scope

      NA

      In Scope

      • Documentation

      Approach(Required){}

      Rename the file docs/architecture/agents.md to docs/architecture/architecture.md and update it moving from the concepts of Primaza Cluster and Worker Cluster to the more generic Application Namespace, Service Namespace, and Primaza Control Plane ones.
      Describe the Application/Service namespace initialization (i.e., when a new Application/Service namespace is created matching resources are pushed by the ClusterEnvironment controller), and cleanup logic (i.e., ownership and finalizers).
      Also modify the ClusterEnvironment doc with the main concepts and reference to docs/architecture/architecture.md.

      Demo requirements(Required)

      NA

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      • Docs
        Documentation is updated with description of new application/service namespaces reconciliation

      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

              fmehta@redhat.com Feny Mehta
              fmehta@redhat.com Feny Mehta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: