How to Deploy the Camunda application with Nginx ingress controller

Camunda 7 Topics Discussion & Questions
,
1

All,

I’m using spring boot based camunda application and depolying my application in azure kubernetes with nginx ingress controller. upon on deploying l’m unable to login into camunda cockpit.

Is there any documentam or suggestions?

Thank you in advance for the help.

Error Screen Shot:

error1
error11898×888 58.9 KB

Snippet for _ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    field.cattle.io/publicEndpoints: '[{"addresses":["1x.xx.x.xx7"],"port":80,"protocol":"HTTP","serviceName":"default:helloworld","ingressName":"default:helloworld","path":"/poc(/|$)(.*)","allNodes":false},{"addresses":["1x.xx.x.xx7"],"port":443,"protocol":"HTTPS","serviceName":"default:helloworld","ingressName":"default:helloworld","path":"/poc(/|$)(.*)","allNodes":false}]'
    kubernetes.io/ingress.class: nginx
    meta.helm.sh/release-name: helloworld
    meta.helm.sh/release-namespace: default
    nginx.ingress.kubernetes.io/rewrite-target: /poc/$2
  creationTimestamp: "2020-08-24T20:20:16Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: helloworld
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: helloworld
    app.kubernetes.io/version: 3.0.0
    helm.sh/chart: helloworld-3.0.0
  name: helloworld
  namespace: default
  resourceVersion: "2679630"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/helloworld
  uid: b3f700cc-1c4c-4961-9f70-42399a50536d
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: helloworld
          servicePort: http
        path: /poc(/|$)(.*)
status:
  loadBalancer:
    ingress:
    - ip: 1x.xx.x.xx7
2

Hi @ramakrishnan707,

I havn’t use an enviroment like yours, but maybe it’s worth to have a look here: https://docs.camunda.org/manual/7.13/introduction/architecture/#session-state-in-a-clustered-environment

and check the default settings of your load balancer.

Hope this helps, Ingo

3

@Ingo_Richtsmeier thanks for your direction. i have tried to enable the sticky session to nginx ingress controller. following snippet i have added to my _ingress.yaml file. still issue not resolved. did i missing anything

  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /helloworld/$2
    nginx.ingress.kubernetes.io/affinity: "cookie"
    nginx.ingress.kubernetes.io/session-cookie-name: "route"
    nginx.ingress.kubernetes.io/session-cookie-expires: "172800"
    nginx.ingress.kubernetes.io/session-cookie-max-age: "172800"
  path: /helloworld(/|$)(.*)
4

Hi @ramakrishnan707,

sorry, I don’t know.

I remember that the last time I handled a similar issue in a different environment, I used the developer console of the browser to track down the issue.

Inspecting the headers of the requests in the console lead me to the solution there…

Hope this helps, Ingo