fix: add constraints for ES and Basic auth in noSecondaryStorage mode #4170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem does the PR fix?
The Helm chart continues to enable Elasticsearch, even though the no-db flag
global.noSecondaryStorage=trueis set. Output:We still need to configure OIDC authentication with "no-secondary-storage" mode as Basic authentication is not supported.
There is some bad UX in the Helm chart, as users only discover this limitation when inspecting logs of crash-looping Zeebe Brokers. Example:
What's in this PR?
I'm adding 2 new constraints
noSecondaryStoragemode with basic auth, it's not supportedelasticsearch.enable: this should be false whennoSecondaryStorageis true (this config is different fromglobale.elasticsearch.enable)Checklist
Please make sure to follow our Contributing Guide.
Before opening the PR:
make go.update-golden-only.After opening the PR:
#closes camunda/camunda#38186