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

Primazactl: add namespace to cluster environment

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • Primaza 0.1
    • None
    • Service Binding
    • None
    • AppSvc Sprint 236

      Owner: Architect:

      Martin Mulholland

      Story (Required)

      As a Primaza Administrator, I would like to easily set up Applications and Services namespaces so that I can discover services and bind them to applications.

      Background (Required)

      For a demo the cluster environment currently needs manual steps to add the namespace ro an application agent and service agent.

      Glossary

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

      Out of scope

      Update primaza

      In Scope

      Update primazactl

      Approach(Required)

      As part is application or service namespace creation update the cluster environment in main as follows:

      for service agent:

      spec:

           serviceNamespaces:

                - <service-namespace>

      for application agent 

      spec:

           applicationNamespaces:

                - <application-namespace>

       

      Note namespace values are an array so may need to start an array or add to an existing array. 

      Demo requirements(Required)

      Yes, just show cluster environment with values added

      Dependencies

      None

      Edge Case

      None

      Acceptance Criteria

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

      Development:
      primazactl updates cluster environment

      QE: Covered by existing test.
      tests checks agent deploys succesfully

      Documentation: No

      Upstream:  Not Applicable

      Downstream:  Not Applicable

      Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
      fix/Breaking change/Deprecated Functionality/Technology Preview>

      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

            mmulholl Martin Mulholland
            mmulholl Martin Mulholland
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: