| commit | fec27ccdd5fc0c8fc4ff749697fd147407acfdc6 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Aug 14 13:13:41 2024 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Aug 15 10:29:58 2024 +0200 |
| tree | 36041534e70cbcebcdbde54c5615e6248d0424bb | |
| parent | bec6aa583c517f61b271468d706d38e1ffca1f5f [diff] |
[COMMON][TIMESCALEDB] TemporalDB and securityContext settings - make pod/containerSecurityContext settings more configurable in _pod.tpl - fix MariaDB statefulset - Fix temporal statefulset to comply with security rules - Set timescaleDB via RepositoryGenerator Issue-ID: OOM-3310 Change-Id: I870f1e835020c2b30225741e700d1a6abfba8ad3 Signed-off-by: Andreas Geissler <andreas-geissler@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.