Skip to content

Commit 375d5e4

Browse files
renovate[bot]github-actions[bot]danbarrclaude
authored
Update stacklok/toolhive-registry-server to v1.4.11 (#979)
* Update stacklok/toolhive-registry-server to v1.4.11 Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * Document global.postgres fallback from registry-server v1.4.11 The Helm chart at v1.4.11 adds a global.postgres.{host,port,sslMode} fallback so umbrella charts can set the database host once instead of repeating it per subchart. Cover the standalone Helm guide and the enterprise platform deployment guide, parallel to the existing global.redis docs. * Tighten subchart fallback section in deploy-helm - Clarify 'umbrella chart' instead of bare 'umbrella' - 'Database host' is more accurate than 'database connection' since only host/port/sslMode are inherited - Split the mid-sentence spaced hyphen into two sentences per the project style (spaced hyphens belong in list-style contexts, not prose) * Frame subchart Postgres section as enterprise Co-authored-by: Dan Barr <danbarr@users.noreply.github.com> * docs(registry): use enterprise-context callout instead of gating badge for global.postgres The global.postgres fallback is a generic Helm global.* mechanism usable by any umbrella chart, not an enterprise-gated feature, so the EnterpriseBadge on the section heading mislabeled it. Replace it with an :::enterprise context callout that still routes full-platform users to the platform-wide PostgreSQL defaults, and keep the section description OSS-neutral. --------- Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Dan Barr <danbarr@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
1 parent e4b2d6d commit 375d5e4

3 files changed

Lines changed: 60 additions & 1 deletion

File tree

.github/upstream-projects.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
projects:
3030
- id: toolhive-registry-server
3131
repo: stacklok/toolhive-registry-server
32-
version: v1.4.10
32+
version: v1.4.11
3333
docs_paths:
3434
- docs/toolhive/guides-registry
3535
- docs/toolhive/concepts/registry-criteria.mdx

docs/platform/enterprise-platform/deployment.mdx

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -289,6 +289,32 @@ override. When set, it takes precedence over `global.redis.host` and
289289

290290
:::
291291

292+
#### Global PostgreSQL defaults
293+
294+
The Registry Server reads its database host, port, and SSL mode from
295+
`global.postgres` when its own
296+
`toolhive-registry-server.upstream.config.database.host` is empty. This is the
297+
same pattern as `global.redis` above, intended for umbrella deployments that
298+
share a PostgreSQL instance across several backing services. The block is
299+
optional: when `global.postgres.host` is empty, the default is inactive and each
300+
subchart uses its own `config.database` block.
301+
302+
```yaml title="values.yaml (global PostgreSQL addition)"
303+
global:
304+
postgres:
305+
# When empty, the global default is inactive.
306+
host: 'postgres.example.com'
307+
port: 5432
308+
sslMode: 'require'
309+
```
310+
311+
Only `host`, `port`, and `sslMode` are inherited from the global block. The
312+
database user, database name, and credentials still go under the subchart's own
313+
`config.database` block (and `extraEnv` for the password Secret reference, as
314+
the example above shows). A locally set
315+
`toolhive-registry-server.upstream.config.database.host` always wins over
316+
`global.postgres.host`.
317+
292318
### 4. Install the chart
293319

294320
Install the chart into the `stacklok-system` namespace you created earlier.

docs/toolhive/guides-registry/deploy-helm.mdx

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,39 @@ config:
7373
sslMode: require
7474
```
7575
76+
### Share a database host across subcharts
77+
78+
When the Registry Server chart runs as a subchart of an umbrella chart whose
79+
bundled services share a single PostgreSQL instance, you can set the database
80+
host once at the umbrella level under `global.postgres` instead of repeating it
81+
per subchart. This is a standard Helm `global.*` mechanism, so any umbrella
82+
chart can use it:
83+
84+
```yaml title="values.yaml (umbrella excerpt)"
85+
global:
86+
postgres:
87+
host: 'postgres.example.com'
88+
port: 5432
89+
sslMode: 'require'
90+
```
91+
92+
When `config.database.host` on the Registry Server subchart is empty, the chart
93+
falls back to `global.postgres.{host,port,sslMode}` (port defaults to `5432`). A
94+
locally set `config.database.host` always wins, so per-subchart overrides keep
95+
working. Only `host`, `port`, and `sslMode` are inherited. The `user`,
96+
`database`, and credentials still go in the subchart's own `config.database`
97+
block.
98+
99+
:::enterprise
100+
101+
If you run the full Stacklok Enterprise platform, its canonical umbrella chart
102+
already wires up `global.postgres`, so you set the shared database host once at
103+
the umbrella level rather than per subchart. See the
104+
[platform-wide PostgreSQL defaults](../../platform/enterprise-platform/deployment.mdx#global-postgresql-defaults)
105+
for the credential Secrets and the other components that read `global.postgres`.
106+
107+
:::
108+
76109
## Provide database credentials
77110

78111
Database credentials use the pgpass file pattern. Create a Kubernetes Secret

0 commit comments

Comments
 (0)