mlangbehn commented on a change in pull request #13: Add script and 
instructions for using Minikube
URL: 
https://github.com/apache/incubator-openwhisk-deploy-kube/pull/13#discussion_r122543353
 
 

 ##########
 File path: minikube/deploy_minikube.sh
 ##########
 @@ -0,0 +1,61 @@
+#!/bin/bash
+
+DIR=$( cd "$( dirname "$0" )" && pwd )
+
+echo "Enabling promisc mode in minikube"
+minikube ssh sudo ip link set docker0 promisc on
+
+echo "Launching configure job"
+kubectl apply -f $DIR/../configure/openwhisk_kube_namespace.yml
+kubectl apply -f $DIR/../configure/configure_whisk.yml
+
+
+printf "Waiting for invoker StatefulSet to exist"
+TIMEOUT=0
+TIMEOUT_COUNT=100
+until $(kubectl -n openwhisk get statefulset invoker &> /dev/null) || [ 
$TIMEOUT -eq $TIMEOUT_COUNT ]; do
+    printf "."
+    let TIMEOUT=TIMEOUT+1
+    sleep 5
+done
+echo
+
+if [ $TIMEOUT -eq $TIMEOUT_COUNT ]; then
+  echo "Gave up waiting for the invoker StatefulSet"
+  exit 1
+fi
+
+echo "Patching the invoker StatefulSet to downgrade the docker API version"
+kubectl -n openwhisk patch statefulset invoker --type=json -p '[{"op": "add", 
"path": "/spec/template/spec/containers/0/env/-", "value": {"name": 
"DOCKER_API_VERSION", "value": "1.23"}}]'
+
+echo "Deleting existing invoker pod so it will get recreated with new env"
+kubectl -n openwhisk delete po/invoker-0
+
+CONFIGURE_POD=$(kubectl get pods --all-namespaces -o wide | grep configure | 
awk '{print $2}')
+
+printf "Waiting for the configure job to complete"
+PASSED=false
+TIMEOUT=0
+TIMEOUT_COUNT=25
 
 Review comment:
   On my test VM (Ubuntu 16.04, 16 GB RAM, 8x 2.6 GHz CPU), this timeout wasn't 
long enough. Switching `TIMEOUT_COUNT` to 500 was also not long enough. Running 
`kubectl -n openwhisk logs [configure-job] -f` eventually shows an ansible 
failure on either consul or couchdb (play and task appears to be inconsistent).
   
   @tobias, are you seeing any similar issues?
 
----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to