You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/01/18 12:33:11 UTC

[GitHub] danielwhatmuff commented on issue #414: adding troubleshooting for install packages failure

danielwhatmuff commented on issue #414: adding troubleshooting for install packages failure
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/pull/414#issuecomment-455531457
 
 
   Hey @dgrove-oss thanks for merging. 
   
   I did encounter a few issues with the install of openwhisk on kubernetes so have been taking a look through the installation process which runs upon a `helm install` and noticed there is quite a lot going on as part of `couchdb-init-job.yaml` and `install-packages-job.yaml` - for example the [myTask.sh](https://github.com/apache/incubator-openwhisk-deploy-kube/blob/master/helm/openwhisk/configMapFiles/installPackages/myTask.sh) script clones 5 repos from Github and executes a further 6 bash scripts. Also [initdb.sh](https://github.com/apache/incubator-openwhisk-deploy-kube/blob/master/helm/openwhisk/configMapFiles/initCouchDB/initdb.sh) clones another repo and runs 4 ansible playbooks.
   
   I wondered if it would be possible to move any of this stuff into the build and release phase so that the helm install can just pull prebaked containers from a registry and either inject environment variables or mount configmaps to pods. With the aim being that provisioning openwhisk on kube is faster and more reliable.
   
   Interested to hear your thoughts.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services