-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG-python/deployment] deploying on DNS with prefix #5792
Comments
@frascuchon This seems like a simple error caused by a missing environment variable or routing to match NUXT resources. What do you think? |
@aleksvercau One thing I noticed: In nginx, should |
I am using regexes in the prefix, this rewrite target matches the regex. |
Hi @aleksvercau! You should define the |
Hi @frascuchon ! Thanks for the tip. However, now I get {"detail":"Not Found"}, so there's still something wrong with the redirects. Any idea what it could be? |
Can you check the request URL running the |
I found an error with the slashes. You should add the final |
# Description <!-- Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. --> Closes #5792 **Type of change** <!-- Please delete options that are not relevant. Remember to title the PR according to the type of change --> - Bug fix (non-breaking change which fixes an issue) **How Has This Been Tested** <!-- Please add some reference about how your feature has been tested. --> **Checklist** <!-- Please go over the list and make sure you've taken everything into account --> - I added relevant documentation - I followed the style guidelines of this project - I did a self-review of my code - I made corresponding changes to the documentation - I confirm My changes generate no new warnings - I have added tests that prove my fix is effective or that my feature works - I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
Describe the bug
I am using the k8s deployment to deploy Argilla. I updated the
examples/deployments/k8s/argilla-chart/values.yaml
file to use our DNS and use https. The idea is to have it run on our DNS with a specific prefix, like all our other services deployed in kubernetes. However, adding a prefix breaks the application.Stacktrace and code to create the bug
This is what is specified in my values file for the ingress:
And this is how I updated the ingress:
When I tried deploying on the plain DNS, without the prefix, it all works fine, when navigating to the url I land on the login page, as expected. When I add the prefix however, the p[age cannot be loaded. In the console I see the following issues:
And the following errors for multiple files:
when I manually add the prefix to those urls (ex. https://mydns/argilla/_nuxt/3045c38.js net) that cannot be found, the .js is loaded, so it looks like the _nuxt resources are not redirected properly when using a prefix.
I tried adding the BASE_URL environment variable, but that didn't fix it.
Expected behavior
Proper loading and functioning of interface when using a prefix.
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: