You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(deps): bump packdb appVersion to release-5.0.1-0.20260709071413.53735f172429 (#5)
## Summary
Bump `appVersion` in `helm/Chart.yaml` to
`release-5.0.1-0.20260709071413.53735f172429`
— the build the engine/metadata `:latest` GHCR tags were just re-pointed
to —
regenerate the `helm/README.md` badge, and refresh the image-overrides
example.
> [!NOTE]
> Opened automatically by packdb's `promote-ghcr-latest` workflow
(weekly
> Monday refresh or a manual promotion) right after it re-pointed the
> engine/metadata `:latest` GHCR tags at this build, so `:latest` and
this
> repo's pinned tags move together. An unmerged PR is overwritten by the
> next run.
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Low Risk**
> Routine image pin and doc/README refresh; the workflow change only
alters when the e2e suite runs, not chart runtime behavior.
>
> **Overview**
> Bumps **`helm/Chart.yaml` `appVersion`** (and the **`helm/README.md`**
badge) to **`release-5.0.1-0.20260709071413.53735f172429`**, aligning
the chart’s default engine/metadata tags with the latest GHCR promotion.
The **image-overrides** doc example uses the same tag pair.
>
> Refactors **`.github/workflows/helm-test.yaml`** so the **`helm-test`
job always runs and reports** (required check): the detect job now
exports a combined **`skip`** flag for docs-only PRs and
**`release-please`** branches, and each heavy step no-ops when skipped
instead of skipping the whole job with a job-level `if`.
>
> Regenerated **`helm/README.md`** values table also documents
**`engineSpec.extraEnv`** and **`engineSpec.extraEnvFrom`** for custom
S3 credential injection.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
8b1e74f. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
---------
Co-authored-by: gm42 <16498973+gm42@users.noreply.github.com>
Co-authored-by: Giuseppe Mazzotta <giuseppe@firebolt.io>
Firebolt Instance on Kubernetes — Envoy gateway, metadata, auth, and engines
6
6
@@ -34,6 +34,8 @@ Firebolt Instance on Kubernetes — Envoy gateway, metadata, auth, and engines
34
34
| engineSpec.defaultStorage | object | {} | Default PVC storage spec for engines. `storageClassName` is intentionally absent — the cluster default storage class is used. Override here or per-engine to specify a class (e.g. `storageClassName: gp3`). |
35
35
| engineSpec.defaultStorage.accessModes | list |`["ReadWriteOnce"]`| Access modes for the default PVC. |
| engineSpec.extraEnv | list |[]| Extra environment variables for the engine container. Use this to inject AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY (for example via `valueFrom.secretKeyRef`) for a custom S3-compatible store (`managed_table_storage: s3` + `aws.endpoint`). |
38
+
| engineSpec.extraEnvFrom | list |[]| Extra `envFrom` sources for the engine container. Use a `secretRef` to load a Secret holding AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY for a custom S3-compatible store. |
37
39
| engineSpec.hostPathStorageEnabled | bool |`false`| When true, uses hostPath instead of PVC for engine data. |
0 commit comments