0

The NebulaGraph Studio version is v3.7.

Here is my traefik and ingress configuration

---
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: default-headers
  namespace: database
spec:
  headers:
    browserXssFilter: true
    contentTypeNosniff: true
    forceSTSHeader: true
    stsIncludeSubdomains: true
    stsPreload: true
    stsSeconds: 15552000
    customFrameOptionsValue: SAMEORIGIN
    customRequestHeaders:
      X-Forwarded-Proto: https
      Connection: keep-alive, Upgrade
      Upgrade: WebSocket
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: database-tls-secret
  namespace: database
spec:
  secretName: database-tls-secret
  commonName: database-tls-secret
  isCA: false
  privateKey:
    algorithm: ECDSA
    size: 256
  dnsNames:
    - nebula-studio.fleur.cn
  issuerRef:
    name: ca-issuer
    kind: ClusterIssuer
    group: cert-manager.io
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: nebula-studio
  namespace: database
  annotations: 
    app.kubernetes.io/instance: nebula-studio
    app.kubernetes.io/name: nebula-studio
    kubernetes.io/ingress.class: traefik-external
spec:
  entryPoints:
    - websecure
  routes:
    - match: Host(`nebula-studio.fleur.cn`)
      kind: Rule
      services:
        - name: nebula-studio-service
          port: 7001
          passHostHeader: true
      middlewares:
        - name: default-headers
  tls:
    secretName: database-tls-secret

The errors are as follows: enter image description here

I wonder how the Websocket URL empty error under k8s traefik gateway route happened. And does this communication error occur between studio and graphd, or between the browser and studio?

Lisa Liu
  • 139
  • 1
  • 6

0 Answers0