I'll specifically point out that the proxy in webpack.config.js is changed here to assume that the user will port-forward an ingress controller or their own reverse proxy instead of multiple services. This will mean that anyone developing against an existing backend will need to port-forward said ingress controller instead of the services they were previously port-forwarding. This is normally achieved with a command similar to:
kubectl port-forward -n ingress-nginx 8000:80
to expose the relevant backend reverse proxy on port 8000 of the local machine.
I'll specifically point out that the proxy in
webpack.config.jsis changed here to assume that the user will port-forward an ingress controller or their own reverse proxy instead of multiple services. This will mean that anyone developing against an existing backend will need to port-forward said ingress controller instead of the services they were previously port-forwarding. This is normally achieved with a command similar to:to expose the relevant backend reverse proxy on port 8000 of the local machine.