commit | 8a56671acfd33f4f44c2114ba4c17139f8ea0984 | [log] [tgz] |
---|---|---|
author | efiacor <fiachra.corcoran@est.tech> | Fri Nov 18 09:15:43 2022 +0000 |
committer | Michal Jagiello <michal.jagiello@t-mobile.pl> | Fri Nov 18 14:56:28 2022 +0000 |
tree | fb7325f8ce4b9f80ed2cc0ad038133767971092a | |
parent | 0ebd1ae06259318d72ef7b9f14f83e5b3db11870 [diff] |
[STRIMZI] Bump kafka version to 3.2.3 Bump strimzi kafka to 3.2.3 Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I8921fef35550c7b97e463102a18e3596f958871e Issue-ID: OOM-3057 (cherry picked from commit f78db40dae64ae2d7cbfabac1e798db01df1cf07)
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.