Age | Commit message (Collapse) | Author | Files | Lines |
|
This check-in is an updated version of helm charts for so
containers based on review comments
Change-Id: I690430622ecbdcaf099a6165844142841db436dd
Issue-ID: SO-709
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|
|
-cloning project files during pod init-phase
-injecting SQL through a shared volume
Issue-ID: OOM-858
Change-Id: Idc845910d5386c3228fb9a557fb3238823242cea
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Issue-ID: OOM-825
Change-Id: I0cd8748adc7aa1a66cefd4a2b7d660d671a550b3
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
This is a standardization (based on helm community best practices)
of a Helm chart for the Service Orchestrator (so) in ONAP.
How to deploy the so chart (outside of the parent onap chart) from
the local oom/kubernetes codebase.
** need to create/update dependencies defined in the chart's
** requirements.yaml
helm dep update so/
** deploy the so helm chart with the "release" name of 'onap'
helm install so/ -n onap
Change-Id: I22471eb9fe0dec32941e14dc63857222c80ebe20
Issue-ID: OOM-727
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|