Kubernetes cannot access self with service ip












0















Some environment info:




Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-28T15:20:58Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}



istio-1.0.2



I can access all services directly/through ingress all without problems.



But I ran into this weird situation. A service cannot access itself



Say I have svc-a, svc-b, all proxied by istio-ingressgateway. I can access both with the gateway , and call svc-a inside svc-b pod, vice versa. However, I can't call svc-a inside svc-a pod, all requests timed out.










share|improve this question























  • Hi Qiaosen, I tested out this case by creating two services A and B. Opening an interactive terminal in service B, and then making requests to A and to B and both worked, can you provide more details?

    – rinormaloku
    Jan 8 at 21:12


















0















Some environment info:




Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-28T15:20:58Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}



istio-1.0.2



I can access all services directly/through ingress all without problems.



But I ran into this weird situation. A service cannot access itself



Say I have svc-a, svc-b, all proxied by istio-ingressgateway. I can access both with the gateway , and call svc-a inside svc-b pod, vice versa. However, I can't call svc-a inside svc-a pod, all requests timed out.










share|improve this question























  • Hi Qiaosen, I tested out this case by creating two services A and B. Opening an interactive terminal in service B, and then making requests to A and to B and both worked, can you provide more details?

    – rinormaloku
    Jan 8 at 21:12
















0












0








0








Some environment info:




Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-28T15:20:58Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}



istio-1.0.2



I can access all services directly/through ingress all without problems.



But I ran into this weird situation. A service cannot access itself



Say I have svc-a, svc-b, all proxied by istio-ingressgateway. I can access both with the gateway , and call svc-a inside svc-b pod, vice versa. However, I can't call svc-a inside svc-a pod, all requests timed out.










share|improve this question














Some environment info:




Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-28T15:20:58Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}



istio-1.0.2



I can access all services directly/through ingress all without problems.



But I ran into this weird situation. A service cannot access itself



Say I have svc-a, svc-b, all proxied by istio-ingressgateway. I can access both with the gateway , and call svc-a inside svc-b pod, vice versa. However, I can't call svc-a inside svc-a pod, all requests timed out.







kubernetes istio






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 26 '18 at 12:01









Qiaosen HuangQiaosen Huang

578518




578518













  • Hi Qiaosen, I tested out this case by creating two services A and B. Opening an interactive terminal in service B, and then making requests to A and to B and both worked, can you provide more details?

    – rinormaloku
    Jan 8 at 21:12





















  • Hi Qiaosen, I tested out this case by creating two services A and B. Opening an interactive terminal in service B, and then making requests to A and to B and both worked, can you provide more details?

    – rinormaloku
    Jan 8 at 21:12



















Hi Qiaosen, I tested out this case by creating two services A and B. Opening an interactive terminal in service B, and then making requests to A and to B and both worked, can you provide more details?

– rinormaloku
Jan 8 at 21:12







Hi Qiaosen, I tested out this case by creating two services A and B. Opening an interactive terminal in service B, and then making requests to A and to B and both worked, can you provide more details?

– rinormaloku
Jan 8 at 21:12














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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53480694%2fkubernetes-cannot-access-self-with-service-ip%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
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53480694%2fkubernetes-cannot-access-self-with-service-ip%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen