Made client's server.js not bound to a specific host #10223
Merged
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
The client's app.listen() call was trying to listen to the host VITE_APP_HOST. In a minikube environment, this would error out since that address had no DNS routing internal to minikube, and the client pod would fail, as the listen() call attempts to ping the host while starting, and throws an error if it cannot do so.
Removing the host from app.listen just has it listen on 0.0.0.0, which will always succeed.
Subtasks Checklist
Breaking Changes
References
closes #insert number here
QA Steps