[CDS] Service mesh compatibility

Patch on CDS charts dedicated to remove https and cert-related
calls from all files.
This ensure compatibility with patched AAI (IID: OOM-2670) and
lays ground for service mesh use.
Replaces https://gerrit.onap.org/r/c/oom/+/126099
Correction for CDS-Strimzi support in application properties

Issue-ID: OOM-2824

Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I522fe60ca748b7e5f731045dac8ca11b13ae2811
10 files changed
tree: f4c7903f84cad6c87e4e1a6105c739d187c29a83
  1. .ci/
  2. .gitlab/
  3. docs/
  4. kubernetes/
  5. TOSCA/
  6. .gitignore
  7. .gitlab-ci.yml
  8. .gitlint
  9. .gitreview
  10. .pre-commit-config.yaml
  11. .pylintrc
  12. .readthedocs.yaml
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. INFO.yaml
  16. README.md
  17. requirements.txt
  18. tox.ini
README.md

ONAP Operations Manager

Description

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.

Contributing

Please see contributing file to learn on how to contribute

Issues

All issues should be filled in ONAP Jira.