Open Kignoux opened 1 year ago
adel-chouchane
commented
1 year ago Hello, try requesting this url from the api container : http://0.0.0.0:8080/system/ready If you get 404 that means you have a problem in your API deployment else you have a problem in the communication between the UI and the API components.
Kignoux
commented
1 year ago Here is the response from the api container:
[jboss@apicurio-studio-api-deployment-768c7dd544-f5m4b ~]$ curl -v http://0.0.0.0:8080/system/ready
* Trying 0.0.0.0...
* TCP_NODELAY set
* Connected to 0.0.0.0 (127.0.0.1) port 8080 (#0)
> GET /system/ready HTTP/1.1
> Host: 0.0.0.0:8080
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Thu, 20 Apr 2023 09:14:37 GMT
< Expires: Wed, 19 Apr 2023 09:14:37 GMT
< Pragma: no-cache
< Cache-control: no-cache, no-store, must-revalidate
< Content-Type: application/json
< Content-Length: 11
<
* Connection #0 to host 0.0.0.0 left intactIndeed, it seems ok.
Looking at my virtualservice configuration, does apicurio-studio support having the same url for the three pods ?
Thanks for your help
aj84276
commented
1 year ago 
I have similar issue, Any luck on the fix?
adel-chouchane
commented
1 year ago For the CORS issue you need to set the QUARKUS_HTTP_CORS=true in the API and UI pods
Kignoux
commented
1 year ago Hello, I do not have the same issue and I was wondering if apicurio-studio supports to have the same url for all the module like so:
My navigator indicates that i cannot find this url for instance: https://apicurio-studio.mydomain.com/studio-api/currentuser/activity?end=10
Thank you
aj84276
commented
1 year ago For the CORS issue you need to set the QUARKUS_HTTP_CORS=true in the API and UI pods
https://quarkus.io/guides/http-reference
Could not add this property..
Any solution : cess to XMLHttpRequest at 'https://apicurio-api..net/designs' from origin 'https://apicurio.' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Kignoux
commented
1 year ago Hello, Does apicurio-studio supports to have the same url for all the module like so:
UI > https://apicurio-studio.mydomain.com/ API > https://apicurio-studio.mydomain.com/studio-api WS> https://apicurio-studio.mydomain.com/designs
Thanks for your help
airen29
commented
11 months ago I have the same issue
Kignoux
commented
11 months ago Hello,
I resolved this by adding the following environment variables to my deployments:
apicurio-studio-api:
QUARKUS_HTTP_CORS: "true"
QUARKUS_HTTP_CORS_ORIGINS: "*" and apicurio-studio-ui
QUARKUS_HTTP_CORS: "false"
airen29
commented
11 months ago Well my main problem is something you had before (NO CORS)
GET https://apicurio-studio.xyz/studio-api/currentuser/activity?end=10 404 (Not Found)
I have it like:
That's my updated Ingress file:
kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
name: Apicurio-general
annotations:
# ingress.kubernetes.io/rewrite-target: /
ingress.kubernetes.io/proxy-connect-timeout: "3600"
ingress.kubernetes.io/proxy-read-timeout: "3600"
ingress.kubernetes.io/proxy-send-timeout: "3600"
ingress.kubernetes.io/send-timeout: "3600"
nginx.ingress.kubernetes.io/configuration-snippet: |
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
nginx.org/rewrites: |-
serviceName=apicurio-studio-ws rewrite=/; │
serviceName=apicurio-studio-ui rewrite=/; │
serviceName=apicurio-studio-api rewrite=/
{{- with .Values.ingress.annotations }}
{{- toYaml . | nindent 4 }}
{{- end }}
spec:
ingressClassName: nginx
rules:
- host: {{ .Values.ui.hostname }}
http:
paths:
- backend:
service:
name: {{ .Values.ws.name }}
port:
number: {{ .Values.ws.port }}
path: /designs
pathType: Prefix
- backend:
service:
name: {{ .Values.ui.name }}
port:
number: {{ .Values.ui.port }}
path: /
pathType: Prefix
- backend:
service:
name: {{ .Values.api.name }}
port:
number: {{ .Values.api.port }}
path: /studio-api
pathType: Prefix
{{- if .Values.ingress.tls.enabled }}
tls:
- hosts:
- {{ .Values.ui.hostname }}
secretName: {{ .Values.ui.hostname }}-tls
{{- end }}I've also tried original one from helm (as I am installing it from Helm) or from Kubernetes configuration provided in distro/kuberentes but got the same problem.
Hello,
I'm trying to install apicurio-studio on a Kubernetes cluster following the yaml example from the github repository (https://github.com/Apicurio/apicurio-studio/tree/master/distro/kubernetes) adapted with the documentation. The http requests go through an istio gateway virtualservice.
My problem is that even though I do not see any errors in the logs (despite the APICURIO_LOGGING_LEVEL variable set to "debug"), the apicurio-studio-api module is not accessible and responds a 404 not found as shown in the image. The apicurio-studio-ui module seems to work correctly as well as the virtualservie configuration.
Is there a way I can debug furthermore ? Can you see something in my configuration you feel is incorrect ?
Thank you for your help! I tried everything :/
Logs from the apicurio-studio-api container:
Command executed directly from the apicurio-studio-api container:
Here are the Kubernetes configurations: