Pod cannot be reached when it is deployed in an Red Hat Service Mesh without sidecar in OpenShift 4
Issue
-
Not able to reach pod using ingress gateway/NodePort:
$ curl -vv curl -vvv http://10.0.0.10:35639 > Accept: */* > < HTTP/1.1 400 Bad Request < content-type: application/problem+json < content-length: 82 < * Connection #1 to host 10.0.0.10 left intact {"title":"unsupported API name or API version","status":400,"cause":"INVALID_API"} -
Why can't the pod be reached when it is deployed in a Service Mesh without sidecar injection and exposed by a NodePort svc?
-
How to reach a pod using NodePort svc when it is inside the Service Mesh and has no sidecar?
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Service Mesh (OSSM)
- 2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.