Uploaded image for project: 'Application Authorization Framework'
  1. Application Authorization Framework
  2. AAF-697 Handle Multi-Namespaces for OOM
  3. AAF-681

aaf-service pod is preset (not hardcoded) to use the 'onap' kubernetes namespace

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Won't Do
    • Icon: High High
    • None
    • Casablanca Release
    • None
    • AAF Dublin M1 01/11-01/31, AAF Dublin M2 02/01-02/21, Frankfurt M1, Frankfurt M2, Frankfurt M3

      The org.osaaf.aaf.cassandra.props file embedded in the aaf-service container explicitly references the onap namespace as part of the service name for the qualified aaf-caas service name.

      Due to this, when ONAP is deployed with a namespace other than 'onap', the aaf-service pod fails to start and blocks most of the other AAF components from exiting the Init state. 

            Unassigned Unassigned
            jmac jmac
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: