-
Notifications
You must be signed in to change notification settings - Fork 504
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
Services and opaque ports #2426
Comments
This should go into the linkerd2 repo, my bad |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Type:
What happened:
Defining a new service (ElasticSearch) and marking its default port (9200) as opaque makes the service unavailable, returning a 502 Bad Gateway on every request.
What you expected to happen:
I would expect the service to be available. If you remove the opaque-port definition it works smoothly
How to reproduce it (as minimally and precisely as possible):
The first step is to deploy an ElasticSearch cluster (I've deployed one single node cluster) and define the corresponding service. I've just happened to find this problem using ElasticSearch but I don't think the type of service it's relevant for this particular problem.
Then you can just go to any other pod in your cluster and try to perform a regular curl:
You will get a 502 Bad Gateway error and, looking at the logs in the Linkerd sidecar :
Looking at the logs in the Linkerd sidecar of the container where the request is being initiated we can find:
Anything else we need to know?:
You can reach $POD_ID:9200 with no problem at all. I've already talked to @mateiidavid and he asked me to write the issue (for more context on our previous conversation https://linkerd.slack.com/archives/C89RTCWJF/p1621515416063200).
Please, let me know if there's anything I could do to help
Environment:
Thank you very much!
The text was updated successfully, but these errors were encountered: