feat: add server-side API proxying via nginx#6
Merged
Conversation
Previously, the React app tried to call the API server directly from the browser using cluster-internal DNS (forkspacer-api-server:8080), which fails as browsers cannot resolve Kubernetes service DNS names. This change implements server-side API proxying: - Browser calls relative paths (/api/v1/*) - Nginx in operator-ui pod proxies to api-server internally - API requests never leave the cluster from the browser Changes: - Add nginx.conf.template with proxy configuration - Add docker-entrypoint.sh to inject API_SERVER_URL at runtime - Update Dockerfile to use custom nginx config and entrypoint - Update Helm values to use API_SERVER_URL for nginx proxying - Update deployment template to pass API_SERVER_URL to container
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, the React app tried to call the API server directly from the browser using cluster-internal DNS (forkspacer-api-server:8080), which fails as browsers cannot resolve Kubernetes service DNS names.
This change implements server-side API proxying:
Changes: