| commit | 6a704d00d3a598039f926f80600f00a8b25e58de | [log] [tgz] |
|---|---|---|
| author | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Tue Mar 29 14:33:10 2022 +0100 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Thu Mar 31 13:20:32 2022 +0000 |
| tree | 507356b4024be0824abe091839c2865a306e447f | |
| parent | f509a5f5f1a2fdf75c18f73beca71405be818b57 [diff] |
[POLICY] Enable cluster role for k8s-ppnt Cluster role is required for the k8s-ppnt to perform helm deployments on the cluster Issue-ID: POLICY-3748 Signed-off-by: zrrmmua <ramesh.murugan.iyer@est.tech> Change-Id: Ib916803d22f6ecf0ed16e8c75fe52b4e567069ca
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.