Open Bewi42 opened 2 years ago
Discussion here: https://github.com/Apicurio/apicurio-registry/discussions/2134
@EricWittmann the issuel is closed, but the discussion has no final answer / approved solution about how to handle the case, only assumptions are described there. can you please point where one can find exact instructions how to expose apicurio registry under conext path in k8s / reverse proxy scenarion.
Hello, As far I know, there is no working solution to make the UI work when root context is redefined by your hosting solution.
My mistake - I thought that the linked discussion offered a viable workaround. I've re-opened this.
I do think we might be able to add some configurability to the UI to help with this, but I don't have an easy way to test it locally.
Hello @EricWittmann, would you have some news to share on this issue?
Hello,
How do you configure Apicurio so that it knows its base URL when deployed into a Kube pod ?
More details : Apicurio Registry is deployed on a Kube cluster inside a "schemas-registry" pod along with a "schemas-registry-service" Service that is inside a "namespace1" namespace. The Kube cluster assigns the service an internal server name that is : "schemas-registry-service.namespace1" I have an exposition feature that allows me to map the following URL to the service so that it can be accessed from outside the Kube cluster : https://myexposition/namespace1/schemas-registry-service BUT when I try to access this URL, Apicurio redirects me to : http://schemas-registry-service.international-technical-resources/ui/ Instead of : https://myexposition/namespace1/schemas-registry-service/ui/
Is there a configuration variable to allow Apicurio to know that it should redirect me to the exposed URL instead of the internal one ?
Originally posted by @Bewi42 in https://github.com/Apicurio/apicurio-registry/discussions/2134