| commit | e35e9a1adec0675a2044e58e09663e3e436d1ed8 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Apr 02 14:29:04 2024 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Apr 05 12:47:35 2024 +0200 |
| tree | 269c40c7f300ee31b24f7f86e730ff0465e288b9 | |
| parent | f8146d85933c5eab5a8061f21dcfce9b6b6b93d5 [diff] |
[MARIADB] Update mariadb-operator and templates to 0.27.0 Update the Mariadb template to support the mariadb-operator version 0.27.0, which changed the CRD naming and the content structure. Temporarily disable istio-sidecar, as problems with init jobs for MariaDB Issue-ID: OOM-3281 Change-Id: Ia9563a5074a739e4b879a7840bedb1d73fbc1b54 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.