Open jiewpeng opened 1 year ago
I have done it successfully for my project with extra customizations, feel free to ping me to discuss more
still this error is encountering what is the possible solution for this error @sudohainguyen
@sudohainguyen This is still not working for me. My Feast version is 0.31.1 on Amazon Linux 2, and I'm using --root_path
flag, but none of the links in the returned html is prefixed with the root path. Could you share some more details about your extra customizations? Do we need some specific customizations to make it work?
Also, can someone reopen this issue?
Same here as @simonrouse9461 described, the --root_path didn't work.
@sudohainguyen What did you do to make it work?
Same here as @simonrouse9461 described, the --root_path didn't work.
@sudohainguyen What did you do to make it work?
Guys, do we have an update on this issue, the --root_path doesn't seem to solve it
Expected Behavior
Feast UI should work when it is served behind a proxy, on a subpath e.g.
/feast-ui
Current Behavior
Parts of the feast UI works behind a subpath, but not entirely (nothing is displayed, just the feast logo with a "404" text - refer to screenshot). No requests in the network tab of the web browser are hitting 404.
Steps to reproduce
Serve feast UI as you would e.g.
feature_store.serve_ui()
, optionally passing in theroot_path
parameter (it does not help).Set up an nginx pod with the following configuration (i.e. the nginx pod should have
/etc/nginx/conf.d/default.conf
with the following contents -dummy_project
is the project name, andhttp://feast-ui-service:8080
is where the feast UI can be accessed from your nginx pod / container):This configuration works on localhost when nginx can listen on the root path
/
. However, note that the URL after all the redirects is wrong (it does not have the prefix)./p/{project_name}
. Without this, the page will display 404 as above./feast-ui
so the UI app does not receive that path that it is not aware of/p/dummy_project
(without the prefix), which we then proxy into the feast UI app. However, in an actual environment, this setup does not work, because when the url does not contain the/feast-ui
prefix, the ingress will not route it to the nginx pod, so the nginx pod cannot proxy the connection to the right place.Ideally, if the feast ui app is capable of being served on a subpath, only the second
location
block should be required in the nginx configuration. The first and thirdlocation
blocks are workarounds.Specifications
Possible Solution
The app should redirect to relative and not absolute paths