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
I searched the issues and found no similar issues.
Component
Other
Feature
The current ingress configuration is that MinIO takes the default root URL path. Kfp requests should start from kfp/. The finishing slash is important; without it, Nginx forwards user requests to MinIO, which leads to user confusion.
From a user perspective, the KFP entry point is not just important, it's the main entry point. This emphasis guides users and enhances the overall usage of the system.
Note: the nginx has the Ray API Server ingress as well.
Note: the changes requires updates in teh installation scripts and in the documentation.
Are you willing to submit a PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
The current ingress configuration is that MinIO takes the default root URL path. That is the only option to make mc work correctly. Changing Minio URL path to anything else is going to break mc usage, see https://min.io/docs/minio/linux/reference/minio-mc/mc-alias.html
we can run 2 separate ingress controllers: one for KFP as a main user entry point and another one for testing/debugging with MinIO and Ray
it will prevent user confusions
Search before asking
Component
Other
Feature
The current ingress configuration is that MinIO takes the default root URL path. Kfp requests should start from
kfp/
. The finishing slash is important; without it, Nginx forwards user requests to MinIO, which leads to user confusion.From a user perspective, the KFP entry point is not just important, it's the main entry point. This emphasis guides users and enhances the overall usage of the system.
Note: the nginx has the Ray API Server ingress as well.
Note: the changes requires updates in teh installation scripts and in the documentation.
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: