Header propagation with graphql super graph

[waqasraz]

I have an Apollo Router with a supergraph that has header propagation enabled. However, the service in the subgraph running with Bridge-to-Kubernetes (B2K) is not receiving requests to the correct pod. Am I missing something in my setup to ensure the kubernetes-route-as header is properly propagated and processed?

Documentation is limited, so the request is sent as a POST request to the supergraph and then forwarded to the local service URL with the header. Example URL: http://water-application-api.water-application-sbx.svc.cluster.local/graphql.

So, I am sending an API gateway request to the service using the URL above with the appropriate header. Both services are running in separate namespaces, but the requests are not reaching the bod that I intend; they are going to regular pods that are not in dev mode, meaning they are running locally.

[waqasraz]

actually I think I am able to figure it out seems to be working.