camunda-platform-helm
camunda-platform-helm copied to clipboard
[TASK] Test multitenancy in the Helm CI pipeline
@jessesimpson36 what we can do now is allowing to test MT via GH labels so we don't change the default behavior yet we allow users to test MT if they want.
we can add a multiTenancy
key in the tests and make it conditional like we have here:
https://github.com/camunda/camunda-platform-helm/blob/26a13e0f26be665166b7f23345b5c9da18ed1714/.github/workflows/test-integration-main.yaml#L74
Using that var to load an extra val file in the actual tests via TEST_HELM_EXTRA_ARGS
.
Originally posted by @aabouzaid in https://github.com/camunda/camunda-platform-helm/issues/963#issuecomment-1764517364
Just for records, currently, zbctl
(v8.3.0) doesn't support deploying to a multi-tenancy setup. Till that, it's not possible to properly test the MT in our workflow.
For the record, in W46 grooming, still zbctl
doesn't support deploying to a multi-tenancy setup.
Wating for: https://github.com/camunda/zeebe/issues/14477
zbctl update has been de-prioritized so we cannot work on this task for the 8.5 release.