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 2018/11/06 04:28:30 UTC

[GitHub] JiniousChoi opened a new issue #338: Rebooting ubuntu os doesn't keep all nodes of kubead-dind-cluster.alive.

JiniousChoi opened a new issue #338: Rebooting ubuntu os doesn't keep all nodes of kubead-dind-cluster.alive.
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/338
 
 
   I guess this is because of the default restart policy of docker containers.
   But, simply `docker start <master/node-1/node-2> doesn't bring up the k8s cluster with Openwhisk.
   
   I intend to use kubeadm-dind-cluster for local development purpose and yet I don't see any guide about it on any documents in this project.
   
   For now, I have no other choices but deploy the long-taking openwhisk all over again everytime. There's gotta be a better way than this, I hope.

----------------------------------------------------------------
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