New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingress gateway request to headless service 503 #16522
Comments
@MiguelRexAlu I was running into the same issue. Upgraded to 1.2.5 and it's working now. |
@cmanzi Thanks for the suggestion but I just found the issue and I solved it. All my services was created with clusteIP: None and that's make my configuration to fail. I removed that tag and now is working aftwer three weeks of changing configuration. I think that should be part of the documentation in virtual services section. |
cc @frankbu ^^^ |
@cmanzi Can you show us your |
^^^ Sorry, my above question was for @MiguelRexAlu (not @cmanzi). |
@frankbu Hello, I think @cmanzi have a differente problem. Here you can find my api-exchange definition befor I removed
This is my new definition:
|
🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2019-09-18. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions. Created by the issue and PR lifecycle manager. |
Bug description
I'm configuring ISTIO using helm here you can find my istio-config.yaml
Then I deployed a bunch of microservices using istioctl, all of them are simple REST call using http. They can communicate each other with out any issue. If I exposed them with Node Ports I can reach and communicate with them correctly.
Here my svc:
I created an ingress gateway and one VirtualServices to route call from outside the cluster. Here gateway and Virtual Services configuration:
Gateway:
Virtual Services:
When I make a call to the service I always got a 503 Service Unavailable:
Here log output for istio-ingressgateway pod:
[2019-08-23 21:49:34.185][38][warning][upstream] [external/envoy/source/common/upstream/original_dst_cluster.cc:110] original_dst_load_balancer: No downstream connection or no original_dst.
Affected product area (please put an X in all that apply)
[X] Configuration Infrastructure
[ ] Docs
[X] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Communication from outside using ingress gateway Node Port
Steps to reproduce the bug
Version (include the output of
istioctl version --remote
andkubectl version
)Kubernetes
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)
Virtual Server with RHEL 7 and Physical Server with RHEL 7
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.
The text was updated successfully, but these errors were encountered: