| commit | d2b2a3d446a92910fcf3be4c6a3b4254451f730c | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue Apr 30 13:08:03 2024 +0200 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Mon May 06 10:12:26 2024 +0200 |
| tree | 097843313c5cd6b2f3d807377a615682bca90329 | |
| parent | c64f1c0954e631709083499f6d1c80258c7809ee [diff] |
[COMMON] Fix Kyverno policy violations in common/mongodb - set resourceLimit's for emptyDir volumes - use non-root group in mongo pods - make pod filesystem read-only - bump mongodb chart version from 14.12.2 to 14.12.3 - use new version in portal-ng, nbi, multicloud and dcae-tcagen2 Issue-ID: OOM-3293 Change-Id: Ife7445433337ac97a03f8cd22ad551e8745b9717 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
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.