You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have a question. Thanks in advance for any advice you have.
I have a vite js app which my colleague built. When we deploy it with the Docker command docker run -p [port]:[port] foo/bar:baz, it works perfectly. I visit the page and see the forms, images, ..
On the other hand, when I deploy the same container as a kubernetes deployment (behind a ClusterIP Service, same port -> same target port, and place this service behind a prefix route on an https ingress), we visit the page, we get a blank white screen and several 404 - NS ERROR CONTENT CORRUPTED errors. We do see the "vite js" on the browser tab's title and we see a 200 from the main request from the route, so network traffic is getting through, but the dynamic content and images aren't being served. Just a white screen.
We have checked the logs and see that the container is running, serving on 0.0.0.0 + the right port, in good health. Same with the services and ingress. It appears that there may be a setting in vite / node configuration pertaining to:
Header upgrades
CSRF
HTTPs termination
etc
This is a little over my head in terms of React/ node, so if anyone has any direction, we will be grateful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I have a question. Thanks in advance for any advice you have.
I have a vite js app which my colleague built. When we deploy it with the Docker command
docker run -p [port]:[port] foo/bar:baz
, it works perfectly. I visit the page and see the forms, images, ..On the other hand, when I deploy the same container as a kubernetes deployment (behind a ClusterIP Service, same port -> same target port, and place this service behind a prefix route on an https ingress), we visit the page, we get a blank white screen and several 404 - NS ERROR CONTENT CORRUPTED errors. We do see the "vite js" on the browser tab's title and we see a 200 from the main request from the route, so network traffic is getting through, but the dynamic content and images aren't being served. Just a white screen.
We have checked the logs and see that the container is running, serving on 0.0.0.0 + the right port, in good health. Same with the services and ingress. It appears that there may be a setting in vite / node configuration pertaining to:
This is a little over my head in terms of React/ node, so if anyone has any direction, we will be grateful.
Beta Was this translation helpful? Give feedback.
All reactions