| commit | 7284be8ba0d7a77261542cd111d79e4e4ab1c4db | [log] [tgz] |
|---|---|---|
| author | demskeq8 <alexander.dehn@highstreet-technologies.com> | Tue Aug 22 09:06:10 2023 +0000 |
| committer | demskeq8 <alexander.dehn@highstreet-technologies.com> | Tue Aug 22 09:37:12 2023 +0000 |
| tree | 9a3d04b90b5a785f20e3fbc817da4a72817ad75b | |
| parent | ffd944b874af386000d157e58be0475561021340 [diff] |
[COMMON] Rendering issue of templ common.nginxIngress for sub-components Fix context handling for templates common.nginxIngress and ingress.config.port Issue-ID: OOM-3237 Change-Id: Idabcdf8ca564d60e2d2471c7fde38412dc478b50 Signed-off-by: demskeq8 <alexander.dehn@highstreet-technologies.com>
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.