Closed tongpu closed 4 years ago
Currently the location ^/graphql is hardcoded in the Nginx configuration. It should be updated to configure the mapping of URL paths to backend services in Ingress. Here's an example what that might look like:
^/graphql
apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: caluma-demo annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - host: demo.caluma.io http: paths: - path: /graphql backend: serviceName: caluma-backend servicePort: 8000 - path: / backend: serviceName: caluma-assets servicePort: 8080
Had the same problem again: https://github.com/projectcaluma/charts/issues/5
Is there a reason to use nginx at all? Could this not be catched inside an nginx-container in docker-compose in front of caluma-demo?
Currently the location
^/graphql
is hardcoded in the Nginx configuration. It should be updated to configure the mapping of URL paths to backend services in Ingress. Here's an example what that might look like: