You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/10/17 16:43:59 UTC
[GitHub] [apisix-helm-chart] Lyt99 opened a new issue, #374: `apisix.podAntiAffinity` have no effect
Lyt99 opened a new issue, #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374
Hi there, I tried to use `apisix.podAntiAffinity` to let apisix pods to sepreate on different nodes.
But this option had no effect in the latest version of helm chart.
Then I found this commit 31b915a0ffdf4987694c3e669e11afd728452e09 removed `podAntiAffinity`, and did not have a documentation removal of this change.
Should there be a change of documentation and `values.yaml` of this removal? And is there any information about `kube-scheduler will take care of this`?
Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] tokers commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1281698013
@fengxsong Could you take a look when you have time?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] fengxsong commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
fengxsong commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1281715817
@Lyt99 At first, I defined template function `apisix.podAntiAffinity` only for situation where apisix instance use hostnetwork and the kind of apisix is `Deployment`. and then I discovered that the kube-scheduler will pre-filter nodes that do not use host ports when scheduling a Pod with an unbound node, which ensures that each instance will be scheduled to a different node.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] Lyt99 commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
Lyt99 commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1281722346
>
In my situation, I want pods to spread on different nodes to achieve high availability, which prevents from one node down, causes all APISIX pods unavailable.
But it's okay for me to have the reason you've explained above, but maybe need some changes to the documentation. And i'm also considering switch my pods to hostnetwork later.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] Lyt99 commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
Lyt99 commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1282258201
> > > @Lyt99 If you are using deployment that do not use hostnetwork option, and wanna place each apisix instances on different nodes, then you should configure the `apisix.affinity` options.
> >
> >
> > In my situation, I want pods to spread on different nodes to achieve high availability, which prevents from one node down, causes all APISIX pods unavailable.
> > But it's okay for me to have the reason you've explained above, but maybe need some changes to the documentation. And i'm also considering switch my pods to hostnetwork later.
>
> @Lyt99 Would you like to submit a PR to optimize the docs?
@tokers Sure, let me submit a PR later.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] tao12345666333 closed issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
tao12345666333 closed issue #374: `apisix.podAntiAffinity` have no effect
URL: https://github.com/apache/apisix-helm-chart/issues/374
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] fengxsong commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
fengxsong commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1281721534
@Lyt99 If you are using deployment that do not use hostnetwork option, and wanna place each apisix instances on different nodes, then you should configure the `apisix.affinity` options.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] Lyt99 commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
Lyt99 commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1281726329
> @Lyt99 If you are using deployment that do not use hostnetwork option, and wanna place each apisix instances on different nodes, then you should configure the `apisix.affinity` options.
Yes, I'll try it. Thanks for your explanation!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-helm-chart] tokers commented on issue #374: `apisix.podAntiAffinity` have no effect
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #374:
URL: https://github.com/apache/apisix-helm-chart/issues/374#issuecomment-1282099464
> > @Lyt99 If you are using deployment that do not use hostnetwork option, and wanna place each apisix instances on different nodes, then you should configure the `apisix.affinity` options.
>
> In my situation, I want pods to spread on different nodes to achieve high availability, which prevents from one node down, causes all APISIX pods unavailable.
>
> But it's okay for me to have the reason you've explained above, but maybe need some changes to the documentation. And i'm also considering switch my pods to hostnetwork later.
@Lyt99 Would you like to submit a PR to optimize the docs?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org