I am running Gitlab CI runner on Kubernetes and when the cluster starts to 
scale up and down (shows cluster updating on the console) access to the 
whole cluster, or some of the pods and servers gets list because of which
the CI jobs fail. It says

 Post https://10.39.240.1:443/api/v1/namespaces/default/pods: dial tcp 
10.39.240.1:443: i/o timeout
>
>

This only starts happening today and wasn't happening previously. So has 
anything changed in the backend?

I tried using the Ubuntu and COS image, and 1.7.8 and 1.8.4 k8s but the 
problem persists.

I get things like

CLUSTER-IP    EXTERNAL-IP   PORT(S)   AGE       SELECTOR
> svc/kubernetes   10.39.240.1   <none>        443/TCP   16m       <none>
> Unable to connect to the server: read tcp 
> 192.168.0.235:56864->35.190.212.63:443: read: connection reset by peer
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> Unable to connect to the server: dial tcp xx.xx.xx.xx:443: getsockopt: 
> operation timed out
> Unable to connect to the server: dial tcp xx.xx.xx.xx:443: getsockopt: 
> operation timed out
> Unable to connect to the server: dial tcp xx.xx.xx.xx:443: getsockopt: 
> operation timed out
>

Every 1.0s: kubectl get all,no,pdb -o 
> wide                                                                          
>                                                                               
>                                                                               
>  
> MacBook-Ultra.local: Fri Dec  1 13:57:41 2017
>
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port?
> The connection to the server xx.xx.xx.xx was refused - did you specify the 
> right host or port? 
>

-- 
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.
  • [kubernetes-users... Hussain Parsaiyan

Reply via email to