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
Due to the changes in this PR Kubernetes port forwarding is currently broken. Looking into the running pod, it seems the publicly available build of these two containers is simply outdated. The nginx instance running inside the frontend container is still listening to port 80, but the Kubernetes manifest dictates port 8080. This causes the port forwarding, when done as described in CONTRIBUTING.md, to fail as soon as a connection to the service is attempted.
Rebuilding and publishing the frondend container should fix this issue.
Uh oh!
There was an error while loading. Please reload this page.
Due to the changes in this PR Kubernetes port forwarding is currently broken. Looking into the running pod, it seems the publicly available build of these two containers is simply outdated. The nginx instance running inside the frontend container is still listening to port 80, but the Kubernetes manifest dictates port 8080. This causes the port forwarding, when done as described in CONTRIBUTING.md, to fail as soon as a connection to the service is attempted.
Rebuilding and publishing the frondend container should fix this issue.Apparently the most recent image was just not pushed with tag "latest", see https://hub.docker.com/r/volcanosh/vc-dashboard-frontend/tags, which should make fixing things even easier :)
The text was updated successfully, but these errors were encountered: