docs(self-hosted): document hostAliases for SSR fix in evaluator overlay#17
Merged
Conversation
Fixes a real bug every fresh evaluator install hits: Nuxt SSR running inside the frontend pod tries to server-side fetch https://api.plexicus.local/... but the cluster's DNS can't resolve api.plexicus.local (it only exists in the evaluator's laptop /etc/hosts), so SSR fetches fail and pages render empty/broken. The chart already supports `frontend.hostAliases` via charts/frontend/templates/deployment.yaml — this PR just documents the required value so evaluators don't have to diagnose the broken-SSR symptom themselves. The example uses <server-ip> as a placeholder; evaluators substitute the ingress LB EXTERNAL-IP from `kubectl -n ingress-nginx get svc ingress-nginx-controller`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Documents a required Helm values override for self-hosted evaluator installs so Nuxt SSR inside the frontend pod can resolve api.plexicus.local (by injecting an /etc/hosts entry via hostAliases), preventing blank/broken SSR-rendered pages during local evaluation.
Changes:
- Adds a
frontend.hostAliasesexample block tovalues-evaluator.yamlin step 9 of the local-evaluation guide. - Explains the SSR/DNS failure mode and how
hostAliasesfixes it inside the pod. - Uses a
<server-ip>placeholder and points readers to theingress-nginx-controllerserviceEXTERNAL-IP.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
frontend.hostAliasesblock to thevalues-evaluator.yamlexample in step 9 of the local-evaluation guideapi.plexicus.localfails without /etc/hosts injection)<server-ip>placeholder so evaluators substitute their own ingress LB IPWhy this matters
Every fresh evaluator install hits the same bug: pages render empty/broken because Nuxt SSR can't resolve
api.plexicus.localfrom inside the cluster (it only exists in the evaluator's laptop/etc/hosts). The chart already supportsfrontend.hostAliasesviacharts/frontend/templates/deployment.yaml— this PR just documents the required value so evaluators don't have to diagnose the symptom themselves.The same pattern is already in use on the Plexicus dev cluster (
argocd/environments/dev/application.yaml:299).Test plan
/etc/hostsnow contains the HostAliases entry and resolvesapi.plexicus.localto the ingress LB IP🤖 Generated with Claude Code