Bump wire-server to 5.25.0 and fix background-worker PostgreSQL config #867
+20
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wire Server: 5.25.0 Changed charts: - account-pages: 0.9.0-pre.1 → 0.9.0-pre.49 - wire-server: 5.23.0 → 5.25.0 - redis-ephemeral: 5.23.0 → 5.25.0 - rabbitmq: 5.23.0 → 5.25.0 - rabbitmq-external: 5.23.0 → 5.25.0 - databases-ephemeral: 5.23.0 → 5.25.0 - fake-aws: 5.23.0 → 5.25.0 - fake-aws-s3: 5.23.0 → 5.25.0 - fake-aws-sqs: 5.23.0 → 5.25.0 - aws-ingress: 5.23.0 → 5.25.0 - fluent-bit: 5.23.0 → 5.25.0 - kibana: 5.23.0 → 5.25.0 - backoffice: 5.23.0 → 5.25.0 - calling-test: 5.23.0 → 5.25.0 - demo-smtp: 5.23.0 → 5.25.0 - elasticsearch-curator: 5.23.0 → 5.25.0 - elasticsearch-external: 5.23.0 → 5.25.0 - elasticsearch-ephemeral: 5.23.0 → 5.25.0 - minio-external: 5.23.0 → 5.25.0 - cassandra-external: 5.23.0 → 5.25.0 - ingress-nginx-controller: 5.23.0 → 5.25.0 - nginx-ingress-services: 5.23.0 → 5.25.0 - reaper: 5.23.0 → 5.25.0 - restund: 5.23.0 → 5.25.0 - k8ssandra-test-cluster: 5.23.0 → 5.25.0 - webapp: 0.8.0-pre.1876 → 0.8.0-pre.1963 - ldap-scim-bridge: 5.23.0 → 5.25.0 - k8ssandra-operator: 1.16.0 → 1.18.0 - step-certificates: 1.25.0 → 1.28.6 - wire-server-enterprise: 5.23.0 → 5.25.0 - postgresql-external: 0.0.44 → 0.0.45 Build: https://raw.githubusercontent.com/wireapp/wire-builds/5a74084feeb1138925dcb671b333da0c76f88f08/build.json
…ync for wire-server 5.25.0 - Add .background-worker.secrets.pgPassword to sync_pg_secrets() in bin/offline-helm.sh so the PostgreSQL password is synced to background-worker values alongside brig/galley/spar/gundeck - Add postgresql connection config (host, port, user, dbname) to background-worker section in prod-values.example.yaml - Add explicit postgresMigration.conversation=cassandra for both galley and background-worker in prod-values.example.yaml - The background-worker override is critical at Chart 5.25.0 where the Helm chart incorrectly defaults this value to "postgresql" instead of "cassandra", causing User Group to Channel sync jobs to silently skip member synchronization
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
aa181b84)background-workerPostgreSQL configuration and secret syncChanges
1.
offline/tasks/proc_pull_charts.shCherry-picked from #843 — updates wire-builds reference to 5.25.0 (
5a74084).2.
bin/offline-helm.shAdds
.background-worker.secrets.pgPasswordtosync_pg_secrets(). The function previously synced PostgreSQL passwords only to brig, galley, spar, and gundeck — butbackground-workerhas requiredpgPasswordsince Chart 5.24.0.3.
values/wire-server/prod-values.example.yamlpostgresqlconnection config (host, port, user, dbname) and explicitpostgresMigration.conversation: cassandrapostgresMigration.conversation: cassandraAt Chart 5.25.0, the
background-workerHelm chart incorrectly defaultspostgresMigration.conversationtopostgresqlinstead ofcassandra(fixed in 5.26.0). Without the explicit override added in this PR:Nothingand silently skip member synchronizationThis PR adds the explicit
cassandraoverride as a workaround.Related