| commit | 92cab4995fdd00bc4df6b702fe14b059def5abc4 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Dec 15 09:37:42 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Jan 19 07:53:46 2023 +0000 |
| tree | 86322ce29c672289658fd60bc70e9c1d77543392 | |
| parent | 2f43e96c6a84b737590cc4db8a5d53fbac8fd586 [diff] |
[COMMON] Add pre/postfix and customized port option for Istio Ingress Add new options for the created Ingress URLs (preaddr, postaddr) and allow to create Ingress configurations using customized ports Correction added to the installation of the Ingress Gateway. Issue-ID: OOM-3084 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ib31050c169799409c6e968adce7ff41e215e3ff9
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.