| commit | bc4ccb78259dfeb32d412d017f5ab7c2db8452d9 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Sun Feb 05 14:44:05 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Feb 06 09:55:16 2023 +0100 |
| tree | d026c38d59aa12a7d9430d46a14a89902c7b5dd5 | |
| parent | 89ea60c8a96163039700de3b4e641c59bba49ca9 [diff] |
[COMMON] Fix nodePort creation in _service.tpl In case of non-TLS service the nodePort was not reserved and missed to disable tls for the services (tlsEnabled) Issue-ID: OOM-3094 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I7f5102a499f4b262556787b5db682e28a9ebcf81
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.