Page Comparison

...

helm upgrade -i dev local/onap --namespace onap -f integration-override.yaml

# to upgrade robot

# a config upgrade should use the local/onap syntax to let K8 decide based on the parent chart (local/onap)

...

helm upgrade -i dev local/onap --namespace onap -f integration-override.yaml --set robot.enabled=true

# if  both the config and the docker container changes use the enable:false, do the make component, make onap  then enable:true

helm upgrade -i dev local/onap --namespace onap -f /root/integration-override.yaml --set robot.enabled=false

Confirm the assets are removed with get pods , get pv, get pvc, get secret, get configmap for those pieces you dont want to preserve

cd  /root/oom/kuberneties

make robot

make onap

helm upgrade -i dev local/onap --namespace onap -f /root/integration-override.yaml --set robot.enabled=true

kubectl get pods --all-namespaces -o=wide

...

# to check status of a pod like robots pod
...
kubectl -n onap delete pvc  dev-sdnc-db-data-dev-sdnc-db-0
# dev-sednc sdnc is the name from the left  of the get pvc command
 

# same for pv (persistant volumes)
...
kubectl -n onap delete  pv  pvc-c0180abd-4251-11e8-b07c-02ee3a27e357

#same for pv, pvc, secret, configmap, services
kubectl get pods --all-namespaces -o=wide 
kubectl delete  pod dev-sms-857f6dbd87-6lh9k -n onap (stuck terminating pod )
 

# full install
# of NAME=dev instane 
...
# update vm_properties.py
# robtrobot/resources/config/eteshare/vm_properties.py
# cd to oom/kub..kuberneties
Remember: Do the enabled=false BEFORE doing the make onap so that the kubectl processing will use the old chart to delete the POD
# make robot; make onap
# helm upgrade -i dev local/onap --namespace onap -f integration-override.yaml - this would just redeploy robot becuase its configMap only