commit | 6f2c6c2d1cdd755470afd91768f53d9050cc4596 | [log] [tgz] |
---|---|---|
author | AndrewLamb <andrew.a.lamb@est.tech> | Tue Apr 18 12:13:13 2023 +0100 |
committer | AndrewLamb <andrew.a.lamb@est.tech> | Tue Apr 18 12:20:07 2023 +0100 |
tree | e7fa6c44434c6d7d36a4298a45df21867d5fe026 | |
parent | 6356e07a0caa7caef201d64977bd9615f6837853 [diff] |
[COMMON] Fix Authorization Policy Template Fix for: no matches for kind AuthorizationPolicy, when trying to install on deployment with no istio. Issue-ID: OOM-3163 Change-Id: I3e0be55d78e6c88655eeaf267c25b8e6747c5b3c Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
The ONAP Operations Manager (OOM) is responsible for life-cycle management of the ONAP platform itself; components such as SO, SDNC, etc.
It is not responsible for the management of services, VNFs or infrastructure instantiated by ONAP or used by ONAP to host such services or VNFs.
OOM uses the open-source Kubernetes container management system as a means to manage the containers that compose ONAP where the containers are hosted either directly on bare-metal servers or on VMs hosted by a 3rd party management system.
OOM ensures that ONAP is easily deployable and maintainable throughout its life cycle while using hardware resources efficiently.
Full documentation is available in ONAP documentation in operations and administration guides.
Please see contributing file to learn on how to contribute
All issues should be filled in ONAP Jira.