K8s Node routing
We are currently building a k8s instance in AWS. We have a specific user case where we need to route traffic to a specific service on a specific node.
We have managed to get the routing to the sevrice working using ingress rules but we cannot ensure the node. The nodes are create by AWS scaling so the ingress rules would be very dynamic.
It is worth pointing out we are running a daemon set with the service installed on each node.
Our urls look like
ServiceX.NodeX.Domain.com
And our AWS ELB is routing traffic to the specific ec2 instance but then the k8s loadbalancer is doing round robin.
amazon-web-services
kubernetes autoscaling asked Nov 22 at 19:35
Thomas Harris
405313
add a comment |
We are currently building a k8s instance in AWS. We have a specific user case where we need to route traffic to a specific service on a specific node.
We have managed to get the routing to the sevrice working using ingress rules but we cannot ensure the node. The nodes are create by AWS scaling so the ingress rules would be very dynamic.
It is worth pointing out we are running a daemon set with the service installed on each node.
Our urls look like
ServiceX.NodeX.Domain.com
And our AWS ELB is routing traffic to the specific ec2 instance but then the k8s loadbalancer is doing round robin.
amazon-web-services
kubernetes autoscaling asked Nov 22 at 19:35
Thomas Harris
405313
Just a note this is for a multiplayer game and we want to route sessions to the same game service
– Thomas Harris
Nov 22 at 19:38
add a comment |
We are currently building a k8s instance in AWS. We have a specific user case where we need to route traffic to a specific service on a specific node.
We have managed to get the routing to the sevrice working using ingress rules but we cannot ensure the node. The nodes are create by AWS scaling so the ingress rules would be very dynamic.
It is worth pointing out we are running a daemon set with the service installed on each node.
Our urls look like
ServiceX.NodeX.Domain.com
And our AWS ELB is routing traffic to the specific ec2 instance but then the k8s loadbalancer is doing round robin.
amazon-web-services
kubernetes autoscaling asked Nov 22 at 19:35
Thomas Harris
405313
We are currently building a k8s instance in AWS. We have a specific user case where we need to route traffic to a specific service on a specific node.
We have managed to get the routing to the sevrice working using ingress rules but we cannot ensure the node. The nodes are create by AWS scaling so the ingress rules would be very dynamic.
It is worth pointing out we are running a daemon set with the service installed on each node.
Our urls look like
ServiceX.NodeX.Domain.com
And our AWS ELB is routing traffic to the specific ec2 instance but then the k8s loadbalancer is doing round robin.
amazon-web-services
kubernetes autoscaling amazon-web-services
kubernetes autoscaling asked Nov 22 at 19:35
Thomas Harris
405313
asked Nov 22 at 19:35
Thomas Harris
405313
asked Nov 22 at 19:35
Thomas Harris
405313
asked Nov 22 at 19:35
Thomas Harris
405313
asked Nov 22 at 19:35
Thomas Harris
405313
405313
Just a note this is for a multiplayer game and we want to route sessions to the same game service
– Thomas Harris
Nov 22 at 19:38
add a comment |
Just a note this is for a multiplayer game and we want to route sessions to the same game service
– Thomas Harris
Nov 22 at 19:38
Just a note this is for a multiplayer game and we want to route sessions to the same game service
– Thomas Harris
Nov 22 at 19:38
Just a note this is for a multiplayer game and we want to route sessions to the same game service
– Thomas Harris
Nov 22 at 19:38
add a comment |
1 Answer
1
active
oldest
votes
You can use nodeport instead of ingress and loadbalancer , and use a Sticky Sessions configuration in ELB (I use HAproxy instead) in front of nodes to handle stateful requests.
answered Nov 23 at 11:03
Nima Hashemi
463
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437160%2fk8s-node-routing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can use nodeport instead of ingress and loadbalancer , and use a Sticky Sessions configuration in ELB (I use HAproxy instead) in front of nodes to handle stateful requests.
answered Nov 23 at 11:03
Nima Hashemi
463
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
add a comment |
You can use nodeport instead of ingress and loadbalancer , and use a Sticky Sessions configuration in ELB (I use HAproxy instead) in front of nodes to handle stateful requests.
answered Nov 23 at 11:03
Nima Hashemi
463
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
add a comment |
You can use nodeport instead of ingress and loadbalancer , and use a Sticky Sessions configuration in ELB (I use HAproxy instead) in front of nodes to handle stateful requests.
answered Nov 23 at 11:03
Nima Hashemi
463
You can use nodeport instead of ingress and loadbalancer , and use a Sticky Sessions configuration in ELB (I use HAproxy instead) in front of nodes to handle stateful requests.
answered Nov 23 at 11:03
Nima Hashemi
463
answered Nov 23 at 11:03
Nima Hashemi
463
answered Nov 23 at 11:03
Nima Hashemi
463
answered Nov 23 at 11:03
Nima Hashemi
463
463
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
add a comment |
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
It still seems to do round robin. We have the service installed on 3 instances and it seems to just loop through these. This is with NodeType. I think Stickiness will only make a difference once the server is connected which doesn't matter to us as we have a websocket open.
– Thomas Harris
Nov 26 at 21:22
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
did you tied ingress with stickiness ? its pod aware ``` annotations: kubernetes.io/ingress.class: "nginx" ingress.kubernetes.io/affinity: "cookie" ingress.kubernetes.io/session-cookie-name: "route" ingress.kubernetes.io/session-cookie-hash: "sha1" ```
– Nima Hashemi
Nov 28 at 11:44
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437160%2fk8s-node-routing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just a note this is for a multiplayer game and we want to route sessions to the same game service
– Thomas Harris
Nov 22 at 19:38