Open PSanetra opened 1 month ago
@jessesimpson36 link relevant issues to this
Related issues
https://github.com/camunda/camunda-platform-helm/issues/1704 First occurrence of the identity 500 after 5 minutes error ^
https://github.com/spring-projects/spring-security/issues/14633 Spring security layer issue which is pretty similar
https://github.com/camunda-cloud/identity/issues/2865 Identity component tracking of this issue
https://github.com/camunda/camunda-platform-helm/issues/1826 Issue tracking how we should document coredns rewrite rules as a workaround for localhost clusters
https://github.com/keycloak/keycloak/issues/29783 Keycloak issue tracking this (keycloak introduced this bug as a security feature. it's unclear if they will walk this back or make it configurable)
Describe the issue:
I have deployed the camunda in a local kind environment and can successfully access all applications including the identity application, but after some time on that UI I get only HTTP 500 errors from the backend.
The error is resolved for some time when I delete the
IDENTITY_REFRESH_JWT
cookie in my browser, so I guess the backend can not successfully refreshing the token. The refresh token issuer url is not reachable from inside the cluster so probably the identity application is not considering theglobal.identity.auth.issuerBackendUrl
.Actual behavior:
Expected behavior:
global.identity.auth.issuerBackendUrl
is setLogs:
Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.
/etc/hosts
:127.0.0.2 kind-devspace.local
console: enabled: true contextPath: /console startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
operate: contextPath: /operate startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
tasklist: contextPath: /tasklist startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
Disable identity as part of the Camunda core
identity: enabled: true contextPath: /identity env:
Disable keycloak
identityKeycloak: enabled: true fullnameOverride: keycloak postgresql: auth: existingSecret: "camunda-secrets" auth: existingSecret: "camunda-secrets" startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
identityPostgresql: auth: existingSecret: "camunda-secrets" primary: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 readReplicas: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 metrics: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
postgresql: primary: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 readReplicas: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 metrics: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
optimize: enabled: true contextPath: /optimize startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
webModeler: contextPath: /modeler restapi: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 webapp: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 websockets: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
Reduce for Zeebe and Gateway the configured replicas and with that the required resources
to get it running locally
zeebe: clusterSize: 1 partitionCount: 1 replicationFactor: 1 pvcSize: 10Gi startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
zeebeGateway: replicas: 1 contextPath: /zeebe startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
connectors: enabled: true contextPath: /connectors inbound: mode: disabled startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5
elasticsearch: master: replicaCount: 1
Request smaller persistent volumes.
data: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 coordinating: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 ingest: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5 metrics: startupProbe: enabled: true initialDelaySeconds: 0 periodSeconds: 2 failureThreshold: 600 readinessProbe: initialDelaySeconds: 0 periodSeconds: 5