Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Settings to disable redirect to proxies #897

Closed
futujaos opened this issue Dec 2, 2024 · 3 comments
Closed

Settings to disable redirect to proxies #897

futujaos opened this issue Dec 2, 2024 · 3 comments

Comments

@futujaos
Copy link

futujaos commented Dec 2, 2024

Some actions like table download from UI generates URL to http proxy LB FQDN, but some installations may not have a public IP for proxies so such URLs will be unavailable. Let's made a property in YTsaurus k8s spec in ui section which will replace all such URLs with UI itself to handle requests through UI itself.

Screenshot 2024-12-02 at 14 03 49
@futujaos futujaos changed the title Property to disable redirect to proxies Settings to disable redirect to proxies Dec 2, 2024
@vrozaev
Copy link
Collaborator

vrozaev commented Dec 13, 2024

From SIG UI meeting:

Let's made a property in YTsaurus k8s spec in ui section which will replace all such URLs with UI itself to handle requests through UI itself.

No, we should not do that, we need to make http proxy available to the user. If we will pass traffic via UI it might be overloaded.

@ma-efremoff
Copy link
Collaborator

ma-efremoff commented Dec 16, 2024

No, we should not do that, we need to make http proxy available to the user. If we will pass traffic via UI it might be overloaded.

Please pay attention for the comment. UI is not able to handle same load as backend.
Anyway there is an option that allows to enable behaviour you want, please see directDownload (it is enabled by default).

@futujaos
Copy link
Author

thanks, directDownload will work for us by now

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants