Zeebe Tasklist Session Expires Immediately Kubernetes Ingress

Camunda 8 Topics Discussion & Questions
1

I deployed a Zeebe Cluster, Operate and Tasklist on local kubernetes. Everything starts and runs.

I added ingress to both operate and tasklist in one ingress file Pasted below.
The ingress works for both.
I can log into Operate with no issues.
However tasklist loads the logon page and immediately gives a session timeout if logging on with a 403 from graphql.

If I use

kubectl port-forward svc/tasklist-zeebe-tasklist-helm 8081:80

Tasklist works fine. Is there anything in the authorization that is dependent on hostname that should be configured?

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: operate
spec:
  ingressClassName: nginx
  rules:
  - host: "operate.127.0.0.1.sslip.io"
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: operate-zeebe-operate-helm
            port:
              number: 80
  - host: "tasklist.127.0.0.1.sslip.io"
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: tasklist-zeebe-tasklist-helm
            port:
              number: 80
2

Hey Paul!
Apparently I am not able to give you an answer to the ingress problem right away.
Have you tried to follow this installation guide?

When doing so you do not need to configure your ingress manually. Or are you doing this for a certain reason?

-Thomas

3

Hi @PaulCrofts,
Are you able to make it work? I am also facing similar kind of issue but in AKS, where I cant access both Tasklist and Operate together, I can only access either of the UIs.Let me know if it has worked for you and please share your fix.

https://forum.camunda.io/t/not-able-to-access-operate-and-tasklist-ui-together-in-aks/2739/4

4