Re: DCAE deployment in R2 (oom or heat)
In our experience, this is likely due to the deployment of this particular component, dep-config-binding-service-7b9cfb76b8-l75mp, timed out.toggle quoted message Show quoted text
And this is usually due to docker image pulling taking too long. We are working on a work around for this in the DCAE bootstrap container, ETA EoB today.
In the meanwhile, if you could prepull images before starting helm install, you could try to run the helm install with an additional parameter to override the default (which is alway pull), something like this:
helm install local/onap -n dev --namespace onap --set global.pullPolicy=IfNotPresent
to avoid pulling images...
There is a job, called dcae-bootstrap, that deploys these 8 pods. You can check its logs for details. Because it is a job, the pod is gone once it is done. You may have to use -a to see it.