-
Notifications
You must be signed in to change notification settings - Fork 43
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
Production Ready Apollo Gateway for GraphQL Services issue #10
Comments
You can find the answer here. In essence, if you want to deploy locally you have to create a listing of your services, if you want to deploy using Apollo Studio you should remove those service references in the constructor and rather use Rover CLI to register your services to Apollo Studio. Your gateway will then automatically discover them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Team,
We are new to GraphQL and we built couple of GraphQl Services using Netflix DGS.
Now we would like to federate those services into single endpoint and started working on it by cloning the apollo gateway federation by netflix example dgs-federation-example/apollo-gateway at master · Netflix/dgs-federation-example · GitHub.
This works perfectly fine on my local machine. But When we deploy the node js app to our AWS EKS env, I am not sure how can I access the apollo server. I always see the Server ready at http://localhost:4000/
I have exposed the port 4000 as well but no use.
Here is my code for creating the apollo server. Please help. I have been trying it for couple of weeks now. I didn’t find a production ready federation example also.
Not having any other configs for playground too. Have health check for http server only on top of it. Please suggest on how to spin the apollo server up and running in our K8s environment
The text was updated successfully, but these errors were encountered: