Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 3a2483f) | patch
Revert "[SO] helm chart for cnf-adapter" 37/114537/3
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>
Tue, 3 Nov 2020 15:52:44 +0000 (15:52 +0000)
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>
Thu, 5 Nov 2020 10:17:01 +0000 (11:17 +0100)
commitd24825b061cc84cde2397c71c128be72500d20c7
treec052074bac336bb6dcfc21cd184f289640c0ade1tree | snapshot
parent3a2483fa7d23ad0a057808a0d42d4c7956ce8aa3commit | diff
Revert "[SO] helm chart for cnf-adapter"

This reverts commit a2145f7fa5a4bfadf6782333a879e75730da4f8e.

Reason for revert: it seems to have weird consequences when bumping so version

Issue-ID: SO-3164
Change-Id: Ibf869be9e9dcba915a738605af6d4f823742fbea
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
13 files changed:
kubernetes/so/components/so-appc-orchestrator/resources/config/overrides/override.yaml diff | blob | history
kubernetes/so/components/so-appc-orchestrator/values.yaml diff | blob | history
kubernetes/so/components/so-cnf-adapter/Chart.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/requirements.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/resources/config/overrides/override.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/templates/configmap.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/templates/deployment.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/templates/secret.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/templates/service.yaml [deleted file] blob | history
kubernetes/so/components/so-cnf-adapter/values.yaml [deleted file] blob | history
kubernetes/so/requirements.yaml diff | blob | history
kubernetes/so/resources/config/overrides/override.yaml diff | blob | history
kubernetes/so/values.yaml diff | blob | history
Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).