[kubernetes-users] How to restore a cluster created by kubeadm when kube-controller-manager exited？

If kube-controller-manager exited, no pods can update again. At the same time, kube-controller-manager pod can not be created too, how can I restore this cluster？ Thanks very much. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

It's working as you need? :) On Monday, December 4, 2017, wrote: > thank you all for the support ;-) > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q" group. > To unsubscribe from this group and stop

Re: [kubernetes-users] How to make a container(s) to able to reach to ClusterIP:port or Service's Publilc IP:NodePort?

Did you figure it out? On Mon, Dec 4, 2017 at 10:15 AM, Kyunam Kim wrote: > Understood - thanks! > > On Thursday, November 30, 2017 at 8:55:31 PM UTC-8, Tim Hockin wrote: >> >> If it came in via the public IP, as you said: >> `https://PublicIP:31245/app/rest/init` then the

Re: [kubernetes-users] How to make a container(s) to able to reach to ClusterIP:port or Service's Publilc IP:NodePort?

Understood - thanks! On Thursday, November 30, 2017 at 8:55:31 PM UTC-8, Tim Hockin wrote: > > If it came in via the public IP, as you said: > `https://PublicIP:31245/app/rest/init` > then the 192 address isn't part > of the request. > > On Thu, Nov 30,

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

If your only requirements is to have one pod per node, then I think the best solution, as Tim suggested, is a Daemon Set ( https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/). And yes, it's perfectly reasonable to edit and reapply YAML's. On Mon, Dec 4, 2017, 18:45

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

So re-apply the deployment.yaml is an acceptable solution considering that my only requirement is have one pod for node? Unfortunately I have a very close due date so I would like to find the faster-simpler and quite stable solution to do a code upgrade :) -- You received this message

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

The scheduler makes the decision trying to spread the pods on nodes as you say. But that is just a "signal", other things are taken into account (pods availability zone, in case of AWS, for example, to spread across AZs too) node's resources, etc. So, the default will try to do that, taking into

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

I tried some solutions and one that is working at the moment is simply based to change my deployment.yaml every time. I mean: 1) I have to deploy for the 1' time my application based on a pod with some containers. These pods should be deployed on every cluster node (I have 3 nodes). I did the

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

Would you prefer a Daemon set instead? On Dec 4, 2017 7:28 AM, "Itamar O" wrote: > I'm guessing you have as many replicas as you have nodes, and you used the > "required" affinity policy over the "preferred" one. > If this is the case, then when you try to update the

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

I'm guessing you have as many replicas as you have nodes, and you used the "required" affinity policy over the "preferred" one. If this is the case, then when you try to update the deployment (with the default upgrade strategy), the controller tries the schedule a *4th pod* (with the new image)

[kubernetes-users] Re: add-to-base url is not working

I'm using nginx ingress controller. If you look at the ingress definition, I've tried to map the http request to two different ports 1) TCP (8080) 2) UDP (56888). When I request the url as http://hostName:8080, the request is sent to the resource associated with UDP. trying to find an option

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

Sorry but now I'm facing another problem :-( The deployment with the options podAntiAffinity/podAffinity is working but when I try to update the deployment with the command: kubectl set image deployment/apache-deployment apache-container=xx:v2.1.2 then I get this error:

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

At https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity there is an example (perfect for my case) where 2 files yaml are used: one for redis-cache and the other for web-store. Anyway I'll try to concatenate them. Thanks -- You received this message

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

Not sure where you have 2 YAML's (since you specify the afiinity under the deployment template spec), but if you end up with the need for multiple YAML's you can always concatenate them to a single file by separating with "---". On Mon, Dec 4, 2017 at 1:41 PM wrote: > I'm

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

I'm reading the documentation and it's just what I was looking for. Many thanks! But is there a way to create a single yaml deployment file to ensure that every pod will be deployed in a single node? So a single file to be executed and not 2 different yaml files as in the example -- You

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

I think that if you create a service that matches the pods of the deployment, K8s will attempt to spread out the pods by default. Also, check out "pod anti-affinity" ( https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity-beta-feature ). On Mon,

[kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

Hi all! I would like to know if there is a way to force Kubernetes, during a deploy, to use every node in the cluster. The question is due some attempts that I have done where I noticed a situation like this: - a cluster of 3 nodes - I update a deployment with a command like: kubectl set