Upgrade Failed

Camunda 8 Topics
1

@nathan.loding - Suddenly I am getting below error while trying to upgrade from 8.4.1 to 8.4.2. I experienced the similar issue earlier but after enabling explicit context path for connector module, I was able to resolve the same issue earlier. But somehow it’s not working now. Can you please help me what I am missing here?

root@ip-10-197-33-114:/home/ubuntu# helm upgrade camunda camunda/camunda-platform --set global.identity.auth.tasklist.existingSecret=$TASKLIST_SECRET --set global.identity.auth.optimize.existingSecret=$OPTIMIZE_SECRET --set global.identity.auth.operate.existingSecret=$OPERATE_SECRET --set global.identity.auth.connectors.existingSecret=$CONNECTORS_SECRET --set identity.keycloak.auth.adminPassword=$KEYCLOAK_ADMIN_SECRET --set identity.keycloak.auth.managementPassword=$KEYCLOAK_MANAGEMENT_SECRET --set identity.keycloak.postgresql.auth.password=$POSTGRESQL_SECRET --set global.identity.auth.zeebe.existingSecret=$ZEEBE_SECRET -f camunda-values-v8.4.yaml -n camunda
coalesce.go:289: warning: destination for identity.postgresql.networkPolicy.egressRules.customRules is a table. Ignoring non-table value ()
coalesce.go:289: warning: destination for identity.postgresql.networkPolicy.ingressRules.readReplicasAccessOnlyFrom.customRules is a table. Ignoring non-table value ()
coalesce.go:289: warning: destination for identity.postgresql.networkPolicy.ingressRules.primaryAccessOnlyFrom.customRules is a table. Ignoring non-table value ()
coalesce.go:289: warning: destination for keycloak.postgresql.networkPolicy.egressRules.customRules is a table. Ignoring non-table value ()
coalesce.go:289: warning: destination for keycloak.postgresql.networkPolicy.ingressRules.primaryAccessOnlyFrom.customRules is a table. Ignoring non-table value ()
coalesce.go:289: warning: destination for keycloak.postgresql.networkPolicy.ingressRules.readReplicasAccessOnlyFrom.customRules is a table. Ignoring non-table value ()
W0213 07:35:29.137506 155521 warnings.go:70] spec.template.spec.containers[0].env[13]: hides previous definition of “CAMUNDA_OPERATE_IDENTITY_REDIRECT_ROOT_URL”
W0213 07:35:29.180530 155521 warnings.go:70] spec.template.spec.containers[0].env[15]: hides previous definition of “CAMUNDA_TASKLIST_IDENTITY_REDIRECT_ROOT_URL”
Error: UPGRADE FAILED: cannot patch “camunda-connectors” with kind Ingress: admission webhook “validate.nginx.ingress.kubernetes.io” denied the request: host “xyx.ap-south-1.elb.amazonaws.com” and path “/” is already defined in ingress camunda/camunda-zeebe-gateway && cannot patch “camunda-zeebe-gateway” with kind Ingress: admission webhook “validate.nginx.ingress.kubernetes.io” denied the request: host “xyz.ap-south-1.elb.amazonaws.com” and path “/” is already defined in ingress camunda/camunda-connectors

I attached the helm values file that I used.
camunda-values-v8.4.yaml (7.9 KB)

2

Would you please explain your architecture? This says that camunda-zeebee-gateway is already mapped to “/”. Is this your SAAS or Self Hosted deployment?

3

Hi @arijit.chanda - this is not something I’ve personally encountered, but I can say it’s not related to Camunda but rather with Kubernetes. Doing a quick search for that error message shows quite a few posts online, all of which have slightly different resolutions depending on the configuration (here’s one example thread).

4

This has been fixed once I defined connectors.ingress.path in values file.

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.