| commit | 2b75d34e7507ef7b8dd366eed0afc7c3be6887e0 | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Fri Feb 25 08:56:57 2022 -0500 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Fri Mar 04 19:09:29 2022 +0000 |
| tree | 7a72cb11beda84ae08a11c892b394be58ad204fd | |
| parent | de97263a2ea4b7a134dc3d43784a6178909feabe [diff] |
[COMMON] Update Ingress API Move from using the v1beta1 version of the Ingress API (deprecated in k8s v1.19 and not present in v1.22+) to the stable v1 version. Issue-ID: OOM-2926 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: Icbd4bf3b8a8a0521160e277cde2977aef8a17faf
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.