-
Sub-task
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-
None
-
OOM Sprint 1, OOM Sprint 5
This will allow greater control over deployment of specific containers in the kubernetes cluster.
It uses conditions in helm templates to optionally exclude parts of the kubernetes manifests (YAMLs). The conditions test boolean "disable" flags - one for each ONAP deployment entity. Same condition is applied to other kubernetes entities (service, PVC...) related to the deployment.
The "disable" flags can be listed in the custom values.yaml file. These values are passed to the helm template engine.
For instance, if some ONAP component OOB consists of multiple pods and for some reason you do not need to deploy one of them, you can disable this particular pod by adding the "disable" flag in the custom values file:
myvalues.yaml:
disableAaiSparkyBe: true
And then passing the custom YAML file to the createAll script with '-v' command line option:
./createAll.bash -n onap -a aai -v myvalues.yaml
sparky-be-deployment.yaml:
#{{ if not .Values.disableAaiSparkyBe }} apiVersion: extensions/v1beta1 kind: Deployment metadata: name: sparky-be namespace: "{{ .Values.nsPrefix }}-aai" ... #{{ end }}
In this example, sparky-be deployment will not be installed as part of A&AI component.
Note: Helm always loads the default values file (located under the helm chart of each component) and then the custom value files. So it is not required to duplicate in the custom file values from the default file. Specify only the values you need to override or to add.