[ 
https://issues.apache.org/jira/browse/SUBMARINE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141828#comment-17141828
 ] 

Wanqiang Ji edited comment on SUBMARINE-543 at 6/22/20, 8:50 AM:
-----------------------------------------------------------------

Hi [~wangda], I cannot reproduced this issue :( 
{code:java}
➜  ~ docker ps
CONTAINER ID        IMAGE                  COMMAND                  CREATED     
        STATUS              PORTS                       NAMES
1f14d9ef7049        kindest/node:v1.15.6   "/usr/local/bin/entr…"   3 hours ago 
        Up 3 hours          127.0.0.1:32768->6443/tcp   submarine-control-plane
➜  ~ kubectl get pods -n kube-system
NAME                                              READY   STATUS    RESTARTS   
AGE
coredns-5c98db65d4-cjp47                          1/1     Running   0          
3h11m
coredns-5c98db65d4-z5r74                          1/1     Running   0          
3h11m
etcd-submarine-control-plane                      1/1     Running   0          
3h10m
kindnet-d49cn                                     1/1     Running   0          
3h11m
kube-apiserver-submarine-control-plane            1/1     Running   0          
3h10m
kube-controller-manager-submarine-control-plane   1/1     Running   0          
3h10m
kube-proxy-cb7d4                                  1/1     Running   0          
3h11m
kube-scheduler-submarine-control-plane            1/1     Running   0          
3h10m
➜  ~ kubectl get pods
NAME                                 READY   STATUS      RESTARTS   AGE
pytorch-operator-54854bf847-hdchs    1/1     Running     0          94m
submarine-database-5f74f747d-725zl   1/1     Running     0          94m
submarine-server-6f449bc967-2h6cz    1/1     Running     0          94m
tf-job-operator-c9cd7ccbd-t7nf8      1/1     Running     0          94m
tf-mnist-json-worker-0               0/1     Completed   0          69m
➜  ~ kubectl exec -it submarine-server-6f449bc967-2h6cz /bin/bash
bash-5.0# ping google.com
PING google.com (172.217.31.238): 56 data bytes
64 bytes from 172.217.31.238: seq=0 ttl=36 time=66.763 ms
64 bytes from 172.217.31.238: seq=1 ttl=36 time=71.324 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 66.763/69.043/71.324 ms
bash-5.0#
{code}


was (Author: jiwq):
Hi [~wangda], I cannot reproduced this issue :( 
{code:java}
➜  ~ docker ps
CONTAINER ID        IMAGE                  COMMAND                  CREATED     
        STATUS              PORTS                       NAMES
1f14d9ef7049        kindest/node:v1.15.6   "/usr/local/bin/entr…"   3 hours ago 
        Up 3 hours          127.0.0.1:32768->6443/tcp   submarine-control-plane
➜  ~ kubectl get pods
NAME                                 READY   STATUS      RESTARTS   AGE
pytorch-operator-54854bf847-hdchs    1/1     Running     0          94m
submarine-database-5f74f747d-725zl   1/1     Running     0          94m
submarine-server-6f449bc967-2h6cz    1/1     Running     0          94m
tf-job-operator-c9cd7ccbd-t7nf8      1/1     Running     0          94m
tf-mnist-json-worker-0               0/1     Completed   0          69m
➜  ~ kubectl exec -it submarine-server-6f449bc967-2h6cz /bin/bash
bash-5.0# ping google.com
PING google.com (172.217.31.238): 56 data bytes
64 bytes from 172.217.31.238: seq=0 ttl=36 time=66.763 ms
64 bytes from 172.217.31.238: seq=1 ttl=36 time=71.324 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 66.763/69.043/71.324 ms
bash-5.0#
{code}

> Issues of Submarine KIND version
> --------------------------------
>
>                 Key: SUBMARINE-543
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-543
>             Project: Apache Submarine
>          Issue Type: Bug
>          Components: Doc
>            Reporter: Wangda Tan
>            Priority: Blocker
>
> I'm trying to follow Submarine doc to install a cluster, I found the default 
> version 1.15.6 which is mentioned by: 
> [https://github.com/tangzhankun/Aapche-Submarine/blob/SUBMARINE-528/docs/userdocs/k8s/kind.md]
> Has issues, core DNS pod will fail after start: 
> {code:java}
>  ~ kubectl get pods -n kube-system --context kind-submarine
> NAME                                     READY   STATUS             RESTARTS  
>  AGE
> coredns-5c98db65d4-8n42p                 0/1     CrashLoopBackOff   2         
>  53s
> coredns-5c98db65d4-j8m6t                 0/1     CrashLoopBackOff   2         
>  53s {code}
> I found KIND community reported very similar issue: 
> [https://github.com/kubernetes-sigs/kind/issues/1659]
> I switched to 
> kindest/node:v1.14.10@sha256:6cd43ff41ae9f02bb46c8f455d5323819aec858b99534a290517ebc181b443c6
>  and now it works. 
> Full command to create cluster
> {code:java}
> kind create cluster --image 
> kindest/node:v1.14.10@sha256:6cd43ff41ae9f02bb46c8f455d5323819aec858b99534a290517ebc181b443c6
>  --name submarine {code}
> How to test it (I follow the calico guide: 
> [https://docs.projectcalico.org/getting-started/kubernetes/hardway/test-networking])
> {code:java}
> kubectl run pingtest --image=busybox --replicas=1 -- sleep infinity 
> kubectl get pod -l run=pingtest -o wide
> kubectl exec -ti pingtest-<name> sh
> And ping www.google.com (or other external website should success){code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to