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) before taking down any of the running 3 pods, failing to do so, because the anti-affinity policy will be violated. Try using "preferred" instead of "required".
On Mon, Dec 4, 2017 at 3:57 PM <mderos...@gmail.com> wrote: > 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=xxxxxx:v2.1.2 > > then I get this error: > > apache-deployment-7c774d67f5-l69lb No nodes are available that match all > of the predicates: MatchInterPodAffinity (3). > > > I don't know how to fix. Maybe the podAntiAffinity option need another > kind of setting to update a deployment? > > -- > 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. > -- 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.
