| commit | 8cd7e264e2a8d7f6686065f882b3b2f0663a6690 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Sep 13 13:24:50 2022 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Sep 13 13:27:13 2022 +0200 |
| tree | 5e92ece0497c1f01d8879fc3c07a8209796bd4a6 | |
| parent | ba86c11f138127067d533dbfa9c6729386e438f7 [diff] |
[STRIMZI] Correct NodePort reservation for services Add the missing Nodeport definition for kafka-broker-2 and renumbered the ports Issue-ID: OOM-3033 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I1f5951e652aea097c5ee28f67f93328af66ba234
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.