I am trying to use Kubernetes for a project I am working on, but I am 
having an issue with pod networking.

First, I followed along with the tutorials 
here https://kubernetes.io/docs/tutorials/kubernetes-basics/
Then I set this up with a local environment running minkube and repeated 
all of the exercises.

Now, I have spun up a 4 node cluster (1 master, 3 workers) with vagrant. I 
have been able to successfully join the worker nodes into the cluster. 
Here is the output for "kubectl get nodes -o wide":

NAME      STATUS    ROLES     AGE       VERSION   EXTERNAL-IP   OS-IMAGE    
            KERNEL-VERSION               CONTAINER-RUNTIME
head      Ready     master    1h        v1.9.1    <none>        CentOS 
Linux 7 (Core)   3.10.0-693.11.6.el7.x86_64   docker://1.12.6
worker1   Ready     <none>    1h        v1.9.1    <none>        CentOS 
Linux 7 (Core)   3.10.0-693.11.6.el7.x86_64   docker://1.12.6
worker2   Ready     <none>    1h        v1.9.1    <none>        CentOS 
Linux 7 (Core)   3.10.0-693.11.6.el7.x86_64   docker://1.12.6
worker3   Ready     <none>    1h        v1.9.1    <none>        CentOS 
Linux 7 (Core)   3.10.0-693.11.6.el7.x86_64   docker://1.12.6

I have deployed the image from the above tutorial.
Here is the output for "kubectl get deployments -o wide":

NAME                  DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE      
 CONTAINERS            IMAGES                                        
 SELECTOR
kubernetes-bootcamp   1         1         1            1           44m      
 kubernetes-bootcamp   gcr.io/google-samples/kubernetes-bootcamp:v1  
 run=kubernetes-bootcamp

I have also exposed the deployment.
Here is the output of "kubectl get services -o wide":

NAME                  TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    
      AGE       SELECTOR
kubernetes            ClusterIP   10.96.0.1       <none>        443/TCP    
      1h        <none>
kubernetes-bootcamp   NodePort    10.110.105.36   <none>        
8080:30037/TCP   38m       run=kubernetes-bootcamp 

The pod is up and running (I currently only have one running, but I have 
scaled to 8 replicas and they all showed as running).
Here is the output of "kubectl get pods -o wide":

NAME                                   READY     STATUS    RESTARTS   AGE  
     IP         NODE
kubernetes-bootcamp-5dbf48f7d4-qldkx   1/1       Running   0          46m  
     10.1.1.8   worker1


For an in depth look at the pod, here is the output of "kubectl describe 
pods":

Name:           kubernetes-bootcamp-5dbf48f7d4-qldkx
Namespace:      default
Node:           worker1/10.0.2.15
Start Time:     Tue, 15 May 2018 15:36:40 +0000
Labels:         pod-template-hash=1869049380
                run=kubernetes-bootcamp
Annotations:    <none>
Status:         Running
IP:             10.1.1.8
Controlled By:  ReplicaSet/kubernetes-bootcamp-5dbf48f7d4
Containers:
  kubernetes-bootcamp:
    Container ID:  
 docker://b17539ecb8dc641c2a82dbc1affbcc5b70cea0791318c6721b617032dc401541
    Image:          gcr.io/google-samples/kubernetes-bootcamp:v1
    Image ID:      
 
docker-pullable://gcr.io/google-samples/kubernetes-bootcamp@sha256:0d6b8ee63bb57c5f5b6156f446b3bc3b3c143d233037f3a2f00e279c8fcc64af
    Port:           8080/TCP
    State:          Running
      Started:      Tue, 15 May 2018 15:37:00 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from 
default-token-gr5qg (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          True
  PodScheduled   True
Volumes:
  default-token-gr5qg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-gr5qg
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason                 Age   From               Message
  ----    ------                 ----  ----               -------
  Normal  Scheduled              49m   default-scheduler  Successfully 
assigned kubernetes-bootcamp-5dbf48f7d4-qldkx to worker1
  Normal  SuccessfulMountVolume  49m   kubelet, worker1   MountVolume.SetUp 
succeeded for volume "default-token-gr5qg"
  Normal  Pulling                49m   kubelet, worker1   pulling image 
"gcr.io/google-samples/kubernetes-bootcamp:v1"
  Normal  Pulled                 49m   kubelet, worker1   Successfully 
pulled image "gcr.io/google-samples/kubernetes-bootcamp:v1"
  Normal  Created                49m   kubelet, worker1   Created container
  Normal  Started                49m   kubelet, worker1   Started container


Now, even though everything looks fine, when I run "kubectl exec -ti 
kubernetes-bootcamp-5dbf48f7d4-qldkx bash", here is the message that I get:

error: unable to upgrade connection: pod does not exist


Does anyone have a solution to this?

Thank you!

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to