Repository navigation
Consolidate PRs #191, #195, #200 into 4.2.0 - #216
Merged
Merged
Conversation
values.yaml has documented redash.sqlAlchemyEnablePoolPrePing with a default of "true" since it was added, but the shared env helper never emitted the variable, so setting it did nothing. Upstream: #200 Co-authored-by: brianrudolf <brianrudolf@users.noreply.github.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
REDASH_DATABASE_PASSWORD was hardcoded to the `password` key of the chart-managed `<release>-postgresql` secret. A release pointing the bundled PostgreSQL at an existing secret left Redash referencing a secret that does not exist. Adds the accompanying postgresql.auth.existingSecret and postgresql.auth.secretKeys.userPasswordKey values, which the upstream PR referenced but never declared, so the key does not resolve empty when only existingSecret is set. Default renders are unchanged. Upstream: #195 Co-authored-by: seslly <seslly@users.noreply.github.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Exposes topologySpreadConstraints for the server, workers, scheduler
and migrations job, alongside the existing nodeSelector/affinity/
tolerations settings.
Reimplemented rather than applied: the upstream patch referenced
`.Values.$workerConfig.topologySpreadConstraints` in the worker
template, which is not valid template syntax and made the whole chart
fail to render with `bad character U+0024 '$'`. Workers read the
merged $workerConfig, so per-worker overrides of the shared
worker.topologySpreadConstraints default work. The upstream patch also
used `indent 8` where the surrounding blocks use `nindent 8`, which
would have emitted malformed YAML, and declared the value as `{}`
though the field is a list.
Also applied to the Knative Service template, which the upstream PR
predates. Note that Knative gates this PodSpec field, so it needs the
corresponding config-features flag enabled.
Upstream: #191
Co-authored-by: Mason0920 <Mason0920@users.noreply.github.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 25, 2026
There was a problem hiding this comment.
All reported issues were addressed across 10 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Consolidates the three remaining actionable PRs into a 4.2.0 release. Supersedes and closes #191, #195, #200. Each is a separate commit with the original author credited via
Co-authored-by.SQLALCHEMY_ENABLE_POOL_PRE_PINGpostgresql.auth.existingSecretfor the database passwordtopologySpreadConstraintson all workloadsTwo of these fix values that silently did nothing
#200 —
redash.sqlAlchemyEnablePoolPrePinghas been invalues.yamlwith a documented default of"true", but the shared env helper never emitted the variable. Rendered output contained zero occurrences ofSQLALCHEMY_ENABLE_POOL_PRE_PING, so anyone who set it got nothing. Now emitted across all six workloads.#195 —
REDASH_DATABASE_PASSWORDwas hardcoded to thepasswordkey of<release>-postgresql. Pointing the bundled PostgreSQL at an existing secret left Redash referencing a secret that does not exist. The upstream patch referencedpostgresql.auth.secretKeys.userPasswordKey, which this chart never declared, so the key would have resolved empty when onlyexistingSecretwas set — both values are now declared and documented.Verified across all three paths:
secretKeyRef{name: test-postgresql, key: password}(unchanged from master)existingSecret=my-pg{name: my-pg, key: password}+ userPasswordKey=pgpass{name: my-pg, key: pgpass}#191 was reimplemented, not applied
The upstream patch made the chart fail to render entirely:
It wrote
.Values.$workerConfig.topologySpreadConstraints— a variable can't be used as a field name. Three further problems: it usedindent 8where every surrounding block usesnindent 8(malformed YAML), declared the value as{}though the field is a list, and predated the Knative template.Reimplemented in the chart's existing style, reading the merged
$workerConfigso per-worker overrides work:Applied to server, all workers, scheduler, migrations and the Knative Service. Knative gates this PodSpec field, so it needs the corresponding
config-featuresflag there.Verification
helm lintandhelm templatepass in default and Knative mode. Rendered manifests parsed as YAML: 31 documents,imagePullSecretson all 6 pod controllers, 3/3 distinct worker selectors. With no values set,topologySpreadConstraintsappears zero times — no behaviour change for existing releases. The 4.1.0 probe helper andclusterDomainstill behave correctly.No upgrade steps: unlike 4.1.0, nothing here touches an immutable field.
🤖 Generated with Claude Code