-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add API gateway #167
Add API gateway #167
Conversation
To review after PR #166 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, aside from some comments.
Also, should we set the API gateway port to some fixed value instead of making it flexible? Tested with 8080
and 2000
, those port numbers don't allow the frontend to communicate with the backend services. Port numbers like 80
and 1234
work though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - pz
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Resolves #14, #19, #20, #24
Overview
Previously, our question service was exposed, allowing anyone to use the endpoints. The API gateway provides automatic authentication, as well as provides ingress capabilities.
Currently does not provide load balancing capabilities. Intention is for load balancing to be done by k8s.
Testing instructions
API_GATEWAY_PORT
value to.env
. Note that whatever port you set here will determine how you access the pages.localhost:$API_GATEWAY_PORT
to access frontend.