Closed megglos closed 1 week ago
@aabouzaid can you check whether this is enough to get started with a first iteration to allow the deployment of identity in a cluster? (excluding the zeebe statefulset task) What is a reasonable timeline for completing iteration 1, so we could deploy identity in a cluster?
@megglos, we will start working on phase 1
in the Alpha 5 cycle, so we will work on it directly after the Alpha 4 release.
Hey Team,
The helm chart work has been completed. There is still an issue with the component @Ben-Sheppard will be double-checking when he is back. Let me know if it is ok to merge the related helm work.
yesterday we confirmed execution-identity
is working and in the ready state with @Ben-Sheppard.
created the iteration 2 issue as we completed the first iteration.
https://github.com/camunda/camunda-platform-helm/issues/2294
Describe the use case:
This feature request is about integrating the execution layer identity into a SM cluster. Execution Identity is a new component that is part of the mono-repo https://github.com/camunda/camunda and will be the component to manager uses/authorizations within a cluster going forward and replace the current present identity component.
For more context, also see https://docs.google.com/presentation/d/1VcdJGDqX4Jcjt7w2gf7KvEyLUueHojmg4wxfcZPJoDI/edit#slide=id.g21c05d33edd_0_0
relates to https://github.com/camunda/product-hub/issues/2222
Describe the enhancement/feature:
Desired outcome and acceptance tests:
Additional information: image:
camunda/camunda:SNAPSHOT
Required config for the identity deployment: configmap:
or alternatively the equivalent env vars: