Closed VLZZZ closed 23 hours ago
This should be fixed by #522 , please test and confirm.
@robholland Thanks for this rework.
I can confirm that with #522 we finally removed all of the in-house workarounds which been made so far.
🎉
On Thu, 4 Jul 2024 at 11:50, Valentin Zayash @.***> wrote:
@robholland https://github.com/robholland Thanks for this rework.
I can confirm that with #522 https://github.com/temporalio/helm-charts/pull/522 we finally removed all of the in-house workarounds which been made so far.
— Reply to this email directly, view it on GitHub https://github.com/temporalio/helm-charts/issues/508#issuecomment-2208677731, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAACKW4U5VTKPQYGYQNWRPLZKUSJBAVCNFSM6AAAAABJSDFFFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYGY3TONZTGE . You are receiving this because you were mentioned.Message ID: @.***>
What are you really trying to do?
I'm trying to use
postgresql
as adefault
store and external Elasticsearch as visibility storage.Describe the bug
The installation will fail if I use the following configuration on
values.yaml
(you may notice additional workaround here already, but it's out scope for now)This setup will fail with:
However as I'm using
elasticsearch.external: true
thevisibilityStore
will be set toes-visibility
already so I don't expect to define something else (especially something related to thecassandra
when using only postgresql/elasticsearch ) https://github.com/temporalio/helm-charts/blob/aca701791eccd128f28dc584e3ecee48c1077795/charts/temporal/templates/server-configmap.yaml#L22C1-L26C15However I can mitigate it by faking the section for visibility storage:
Previously I've been using custom workaround for my PoC by simply removing visibility persistence from
range
function for the server-job.yaml template:Overview of my git-patch:
Minimal Reproduction
Environment/Versions
Kubernetes
Additional context