Istio - multiple routing rules performance?
I have a system deployed on Kubernetes and having traffic managed by Istio.
In my system I have to dynamically declare many SNI routing rules (estimation of 10,000 rules). These rules are constantly changing (e.g. routes added / removed all the time, dynamically).
As I understand, I have 2 options:
- Declare single VirtualService with 10,000 rules inside
- Declare 10,000 VirtualServices each one with single rule
Is there a difference between two approaches (performance wise / management wise)? Is there a practical limit of number of Services / Rules which can be defined?
kubernetes istio
add a comment |
I have a system deployed on Kubernetes and having traffic managed by Istio.
In my system I have to dynamically declare many SNI routing rules (estimation of 10,000 rules). These rules are constantly changing (e.g. routes added / removed all the time, dynamically).
As I understand, I have 2 options:
- Declare single VirtualService with 10,000 rules inside
- Declare 10,000 VirtualServices each one with single rule
Is there a difference between two approaches (performance wise / management wise)? Is there a practical limit of number of Services / Rules which can be defined?
kubernetes istio
add a comment |
I have a system deployed on Kubernetes and having traffic managed by Istio.
In my system I have to dynamically declare many SNI routing rules (estimation of 10,000 rules). These rules are constantly changing (e.g. routes added / removed all the time, dynamically).
As I understand, I have 2 options:
- Declare single VirtualService with 10,000 rules inside
- Declare 10,000 VirtualServices each one with single rule
Is there a difference between two approaches (performance wise / management wise)? Is there a practical limit of number of Services / Rules which can be defined?
kubernetes istio
I have a system deployed on Kubernetes and having traffic managed by Istio.
In my system I have to dynamically declare many SNI routing rules (estimation of 10,000 rules). These rules are constantly changing (e.g. routes added / removed all the time, dynamically).
As I understand, I have 2 options:
- Declare single VirtualService with 10,000 rules inside
- Declare 10,000 VirtualServices each one with single rule
Is there a difference between two approaches (performance wise / management wise)? Is there a practical limit of number of Services / Rules which can be defined?
kubernetes istio
kubernetes istio
asked Jan 1 at 8:14
IllidanIllidan
1,99812430
1,99812430
add a comment |
add a comment |
0
active
oldest
votes
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%2f53993992%2fistio-multiple-routing-rules-performance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53993992%2fistio-multiple-routing-rules-performance%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