-
Notifications
You must be signed in to change notification settings - Fork 486
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
The access to the API seems not properly define in the K8S setttings. #1219
Comments
hmm... Do you have an ingress controller running? If so which one in what version? @EricWittmann what part of apicurio handles the resource currentuser/recent/designs/currentuser/recent/designs ? |
@t-rap Thanks a lot for your answer. For your information, I use an nginx ingress controller providing in an helm charts:
The values of the helm charts present in 01-ingress-values.yaml is defined as follow:
The apicurio application is linked to the ingress controller using the ingress file present here: I will continue my investigation and of course, thanks in advance for your help. Regards, |
uh, yep, there's a line missing for apicurio-studio-ws:
could you try this as update? As of now, those configs will be replaced by helm-chart-operator in /distro/helm, as far as i know. If you have helm installed on your cluster, you should give that a go :) |
Hi @t-rap , The issue is not due to your file but to my configuration. In fact, the platform does not allow to use cross origin URL. Therefore, all my API call is forbidden. I have correct the URL in the template and all is working fine. I will writte an installation documents and I will share it to you as soon as possible. Regards, |
Excited to see this one get worked out before I got to it! :) :) |
Hello, have a new info about this documentation? I have the same problem |
@wdesplas ping :) |
Description:
I tried to install the apicurio-studio on the following K8S server version in order to edit an installation guide :
First I have install the keycloack regarding the following guide https://apicurio-studio.readme.io/docs/setting-up-keycloak-for-use-with-apicurio and I have adapted the files present in https://github.com/Apicurio/apicurio-studio/tree/master/distro/kubernetes to fit the storage class needs.
However, I still have an issue with the hub_api. In fact, it seems some configuration is not proper in the docker image.
In fact, once logged in the apicurio UI I have the following error message:
Could you please let me know what I have miss or any guideline?
Expected result:
The hub api must be able to answer to the request properly to be able to handle the requests from the UI.
Note:
Morevover, It will be really usefull for this project adoption to have a documentation explaining how to install all the feature in K8S and other platform step by step.
Thanks in advance.
Regards,
The text was updated successfully, but these errors were encountered: