<p>I am trying to setup a simple POC of Apache OpenWhisk serverless framework running on Kubernetes.  I am using MacOS with Minikube.  Here are the specs:</p>
<pre><code>Kubernetes: v1.20.2
Minikube: v1.17.0
Docker: 20.10.0-rc1, 4.26GB allocated
</code></pre>
<p>Here are the setup steps for Minikube:</p>
<pre><code>$ minikube start --cpus 2 --memory 4096 --kubernetes-version=v1.20.2
$ minikube ssh -- sudo ip link set docker0 promisc on
$ kubectl create namespace openwhisk
$ kubectl label nodes --all openwhisk-role=invoker
</code></pre>
<p>Install OpenWhisk using Helm:</p>
<pre><code>$ helm install owdev ./helm/openwhisk -n openwhisk --create-namespace -f mycluster.yaml
</code></pre>
<p>Configure Whisk CLI:</p>
<pre><code>$ wsk property set --apihost 192.168.49.2:31001
$ wsk property set --auth 23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP
</code></pre>
<p>The <code>192.168.49.2</code> IP address of Minikube was confirmed by typing:</p>
<pre><code>$ minikube ip
</code></pre>
<p>Here is my <code>mycluster.yaml</code> file:</p>
<pre><code>whisk:
  ingress:
    type: NodePort
    apiHostName: 192.168.49.2
    apiHostPort: 31001

nginx:
  httpsNodePort: 31001
</code></pre>
<p>I checked the health of my OpenWhisk setup:</p>
<pre><code>$ kubectl get pods -n openwhisk
NAME                                                          READY   STATUS      RESTARTS   AGE
owdev-alarmprovider-5b86cb64ff-q86nj                          1/1     Running     0          137m
owdev-apigateway-bccbbcd67-7q2r8                              1/1     Running     0          137m
owdev-controller-0                                            1/1     Running     13         137m
owdev-couchdb-584676b956-7pxtc                                1/1     Running     0          137m
owdev-gen-certs-7227t                                         0/1     Completed   0          137m
owdev-init-couchdb-g6vhb                                      0/1     Completed   0          137m
owdev-install-packages-sg2f4                                  1/1     Running     0          137m
owdev-invoker-0                                               1/1     Running     1          137m
owdev-kafka-0                                                 1/1     Running     0          137m
owdev-kafkaprovider-5574d4bf5f-vvdb9                          1/1     Running     0          137m
owdev-nginx-86749d59cb-mxxrt                                  1/1     Running     0          137m
owdev-redis-d65649c5b-vd8d4                                   1/1     Running     0          137m
owdev-wskadmin                                                1/1     Running     0          137m
owdev-zookeeper-0                                             1/1     Running     0          137m
wskowdev-invoker-00-13-prewarm-nodejs10                       1/1     Running     0          116m
wskowdev-invoker-00-14-prewarm-nodejs10                       1/1     Running     0          116m
wskowdev-invoker-00-15-whisksystem-invokerhealthtestaction0   1/1     Running     0          112m
</code></pre>
<p>Finally, I created a simple hello world action following <a href="https://openwhisk.apache.org/documentation.html#actions-nodejs" rel="nofollow noreferrer">these instructions taken directly from the OpenWhisk documentation</a>.  When I try to test the action, I get a network timeout:</p>
<pre><code>$ wsk action create helloJS hello.js
</code></pre>
<blockquote>
<p>error: Unable to create action 'helloJS': Put &quot;https://192.168.49.2:31001/api/v1/namespaces/_/actions/helloJS?overwrite=false&quot;: dial tcp 192.168.49.2:31001: i/o timeout</p>
</blockquote>
<p>I tried turning on debug mode with the <code>-d</code> switch, but could not make much of what feedback I am seeing.</p>
<p>My feeling is that there is either a bug at work here, or perhaps Minikube on Mac was never intended to be fully supported on OpenWhisk.</p>
<p>Can anyone suggest what I might try to get this setup and action working?</p>

Tim Biegeleisen
<p>We stopped maintaining OpenWhisk for Minikube a while ago.  With the availability of a full-fledged Kubernetes cluster built-in to Docker Desktop on MacOS and Windows and <code>kind</code> (<a href="https://kind.sigs.k8s.io" rel="nofollow noreferrer">https://kind.sigs.k8s.io</a>) being available on all of our platforms supporting Minikube was more work than it was worth.</p>
