You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Murchenko (Jira)" <ji...@apache.org> on 2019/10/10 11:37:00 UTC
[jira] [Comment Edited] (IGNITE-9564) Ignite K8 service and sticky
session with AWS K8 deployments
[ https://issues.apache.org/jira/browse/IGNITE-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948473#comment-16948473 ]
Ilya Murchenko edited comment on IGNITE-9564 at 10/10/19 11:36 AM:
-------------------------------------------------------------------
Hello [~mmuzaf]
As I can see AWS Application Load Balancer and Network Load Balancer currently supports sessionAffinity.
I think we should create an instruction how to run Ignite cluster on Kubernetes on AWS EC2, but it can be moved on the next release.
was (Author: imurchenko):
Hello [~mmuzaf]
As I can see AWS Application Load Balancer and Network Load Balancer currently supports sessionAffinity.
I think we should create an instruction how to run Ignite cluster on Kubernetes on AWS EC2, but it can be done on the next release.
> Ignite K8 service and sticky session with AWS K8 deployments
> ------------------------------------------------------------
>
> Key: IGNITE-9564
> URL: https://issues.apache.org/jira/browse/IGNITE-9564
> Project: Ignite
> Issue Type: Task
> Reporter: Denis A. Magda
> Assignee: Ilya Murchenko
> Priority: Major
> Fix For: 2.8
>
>
> _sessionAffinity_ parameter is not supported by AWS Kubernetes which causes the failure of the standard Ignite service deployment:
> http://apache-ignite-users.70518.x6.nabble.com/Error-installing-Ignite-on-K8s-td23999.html
> See how Ignite service configuration have to be updated considering sticky session capabilities of AWS:
> https://aws.amazon.com/elasticloadbalancing/details/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)