Uploaded image for project: 'Application Authorization Framework'
  1. Application Authorization Framework
  2. AAF-697

Handle Multi-Namespaces for OOM

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • None
    • None
    • AAF Dublin M1 01/11-01/31, AAF Dublin M2 02/01-02/21, Frankfurt M1, Frankfurt M2, Frankfurt M3

      Original OOM requirement was "onap" ns.  Customers are requesting changing OOM Namespace.

        1.
        		 aaf-service pod is preset (not hardcoded) to use the 'onap' kubernetes namespace Sub-task Closed Unassigned
        2.
        		 Create a way to Automate SANs based on OOM Namespace Sub-task Closed instrumental
        3.
        		 aaf-service pod in crashed state if not onap namespace is used Sub-task Closed Unassigned
        4.
        		 Adjust current OOM Charts Sub-task Closed instrumental

            Unassigned Unassigned
            instrumental instrumental
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: