Why I cannot run hello example by using minikube

80 views
Skip to first unread message

Joseph Wang

unread,
Mar 11, 2020, 9:11:42 PM3/11/20
to Skupper
Hi 

I tried to create 2 minikube cluster on my local machine. And then follow the skupper hello example to figure out if two cluster can discover each other. But when I use skupper connect TOKEN and then skupper status. The skupper always give me an message 

Skupper enabled for namespace "us-east". Status pending...

and when I use kubectl get pods both returns

kubectl get pods
NAME                                       READY   STATUS             RESTARTS   AGE
hello-world-backend-6d58c544fc-x8wgt       0/1     ImagePullBackOff   0          36m
skupper-proxy-controller-6cdbbb97b-j9mgj   0/1     ErrImagePull       0          41m
skupper-router-6d94c76449-p6q4x            0/1     ImagePullBackOff   0          46m


kubectl get pods
NAME                                        READY   STATUS             RESTARTS   AGE
hello-world-frontend-759cdcf7f9-dqrp5       0/1     ImagePullBackOff   0          36m
skupper-proxy-controller-58c4679d49-tclr9   0/1     ImagePullBackOff   0          41m
skupper-router-746bdbc54f-pxsfn             0/1     ImagePullBackOff   0          37m
skupper-router-c7d75b4b6-srgqz              0/1     ImagePullBackOff   0          28m

Not sure if I can create two minikube cluster to do the tests

Best,

Joseph

Gordon Sim

unread,
Mar 12, 2020, 5:15:09 AM3/12/20
to sku...@googlegroups.com
It is possible, providing you use distinct ip ranges, have a `minikube
tunnel` running for each and the tunnel has an ip that is accessible
from the other cluster.

However it looks like your first issue is with pulling the images from
quay.io. If you run `kubectl describe` against the pods, do you get any
further insight into that? Can you successfully do a `docker pull` on
the images?

(A simpler initial test is to run the example on a single minikube
instance but using two distinct namespaces. However you first need to be
able to get the images.)

Justin Ross

unread,
Mar 12, 2020, 7:40:43 AM3/12/20
to Gordon Sim, sku...@googlegroups.com
I'm currently seeing an image pull problem as well, fwiw.

Once you get past that, here's an alternative approach to using minikube profiles.  This makes the us-east namespace an edge site, so you don't need to do the IP range stuff.

## General

    sudo systemctl stop firewalld

## US East

    export KUBECONFIG=$HOME/.kube/config-us-east
    minikube start -p us-east
    kubectl create namespace us-east
    kubectl config set-context --current --namespace us-east
    skupper init --edge
    skupper connect $HOME/secret.yaml
    kubectl create deployment hello-world-backend --image quay.io/skupper/hello-world-backend
    kubectl expose deployment hello-world-backend --port 8080
    kubectl annotate service hello-world-backend skupper.io/proxy=http

## EU North

    export KUBECONFIG=$HOME/.kube/config-eu-north
    minikube start -p eu-north

    # In a distinct shell:
    #
    #   minikube update-context -p eu-north
    #   minikube tunnel -p eu-north

    kubectl create namespace eu-north
    kubectl config set-context --current --namespace eu-north
    skupper init
    skupper connection-token $HOME/secret.yaml
    kubectl create deployment hello-world-frontend --image quay.io/skupper/hello-world-frontend
    kubectl expose deployment hello-world-frontend --port 8080 --type LoadBalancer
    curl $(kubectl get service hello-world-frontend -o jsonpath='http://{.status.loadBalancer.ingress[0].ip}:8080/')



--
You received this message because you are subscribed to the Google Groups "Skupper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skupper+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/skupper/0dbe5637-64af-6c21-7d3a-4a55ba893c09%40redhat.com.

Gordon Sim

unread,
Mar 12, 2020, 8:07:02 AM3/12/20
to sku...@googlegroups.com
On 12/03/2020 11:40 am, Justin Ross wrote:
> I'm currently seeing an image pull problem as well, fwiw.

Any detail on what the error is? Are you able to pull using docker directly?

Justin Ross

unread,
Mar 12, 2020, 8:56:45 AM3/12/20
to Gordon Sim, sku...@googlegroups.com
I just tried docker pull and it worked.  I'm at work now, so the environment changed, and time has passed.

--
You received this message because you are subscribed to the Google Groups "Skupper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skupper+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages