Enable/Disable settings can be revert if needed, just add CC containers line back to the deployment.yaml
1. Take a backup of the /opt/charts/vco/templates/deployment.yaml
cp /opt/charts/vco/templates/deployment.yaml /home/root/deployment-vco-old.yaml
2. Edit the deployment.yaml file located in /opt/charts/vco/templates/deployment.yaml You need to delete the vco-controlcenter-app from the yaml file. The container definition begins at:
- name: vco-controlcenter-app
{{- if .Values.image.remoteRegistry }}
and ends at
{{- if .Values.enableResourceLimits }}
resources:
limits:
memory: {{ .Values.controlCenterMemoryLimit | quote }}
requests:
memory: {{ .Values.controlCenterMemoryRequest | quote }}
{{- end }}
Everything between(and including) these segments should be deleted. After that running deploy.sh will restart the environment and the control-center container won't be created.
*** The changes are persistent until an eventual upgrade of the environment.
3. Restart all pods
a) restart pods using deploy.sh
/opt/scripts/deploy.sh
b) when all pods are up you should see only 2 containers running for vco pod
You can check running pods using command:
kubectl -n prelude get pods