| commit | 3c81b1d77c53b18e94e282d8bf0250a5563875d0 | [log] [tgz] |
|---|---|---|
| author | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Mon Jul 18 16:54:51 2022 +0100 |
| committer | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Mon Jul 18 16:54:51 2022 +0100 |
| tree | c75edb3d1554ba52d0c92e6d8559b3cd43db62b3 | |
| parent | 19253fcbba119e3c57ccd39690e04afa02e40f33 [diff] |
[POLICY] Add overridable helm paramaters for k8s ppnt Make permitted repository list overridable from values.yaml CofigMap populates the application properties file with required values. Issue-ID: POLICY-4237 Signed-off-by: zrrmmua <ramesh.murugan.iyer@est.tech> Change-Id: Ib48716f12bc5f4d22fbda8e22fd2077e0e982ec3
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.