On Wednesday, June 15, 2016, insomia <[email protected]> wrote: > Hi, > > Sometimes I can`t access kubernetes service. I have two configs: > frontend_deployment.yml and frontend_service.yml. Used service type: > LoadBalancer. Mostly after deploy (after kubernetes apply -f > frontend_deployment.yml) I cant access service, pod is in Running state and > available. > Are you using the same kind, right?
As you said you have one replica, on deploy the pod will be deleted and then created again. That causes downtime, because is first killed and then the new version deployed. If you want to avoid this, you can configure in the deployment type the maxUnavalable (at university now, it's in the docs or in the spec, in k8s.io --> documentation --> reference and the API definition there). That way you force to first create the pod and then kill the other one. Also, if you have 2 replicas you don't need to configure that because there is always one pod alive (it is killed only one by default) Does either of these things makes the trick for you? -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
