feat: add xapi-lrs Helm chart - #115
Merged
Merged
Conversation
Ports the chart from pelotech/charts PR #155 into charts/xapi-lrs so it lives alongside the app. The chart connects to an external PostgreSQL by default (database.driver=pg) with schema migrations in an init container, or runs the embedded PGlite engine (database.driver=pglite) with optional PVC persistence. Ingress/Gateway API route to the xAPI port only; the admin port stays on the Service with an optional ServiceMonitor. Compared to the charts-repo version, the image pin moves up to the current app release (0.8.2) and the README documents the new OCI install location. The chart is versioned independently of the app via a second release-please package (release-type helm, component xapi-lrs-chart, tags xapi-lrs-chart/x.y.z). Chart commits are excluded from the root package so chart-only changes don't bump the app. On chart releases, a new publish-chart job pushes the packaged chart to oci://ghcr.io/pelotech/xapi-lrs/charts (i.e. ghcr.io/pelotech/xapi-lrs/charts/xapi-lrs). The image build jobs now key off the root package's release_created output instead of the aggregate releases_created, which would also fire on chart-only releases. CI gains a helm-chart job linting the chart and rendering the pg/pglite/existingSecret/DATABASE_URL/ingress/gateway permutations. Helm templates are Go-templated YAML, so they are excluded from oxfmt, check-yaml, and yamllint.
This was referenced Jul 23, 2026
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
1 participant
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.
Chart
Same shape as the charts-repo PR: external PostgreSQL by default (
database.driver=pg) with schema migrations in an init container (migration.postgresql.*for a DDL role), or embedded PGlite (database.driver=pglite,replicaCount=1enforced) with optional PVC persistence. Ingress and Gateway API (HTTPRoute + optional ListenerSet) route to the xAPI port only; the admin port stays on the Service with an optional ServiceMonitor. Credentials live in a chart-managed Secret unlessauth.existingSecretis set.Differences from the charts-repo version:
appVersion)Release & publish
charts/xapi-lrsbecomes a second release-please package (release-type: helm, componentxapi-lrs-chart, tagsxapi-lrs-chart/x.y.z,initial-version0.1.0, separate release PRs). Chart commits are excluded from the root package so chart-only changes don't bump the app.publish-chartjob packages andhelm pushes the chart tooci://ghcr.io/pelotech/xapi-lrs/chartson chart releases.release_createdoutput instead of the aggregatereleases_created, which would also have fired (with an empty tag) on chart-only releases.CI & tooling
helm-chartCI job:helm lintplushelm templateacross the pg/pglite/existingSecret/DATABASE_URL/ingress/httproute/listenerset/servicemonitor permutations (all verified locally with helm 4.1, including the pglitereplicaCount>1guard failing as intended).charts/*/templates/is excluded from oxfmt, check-yaml, and yamllint.Note: merging this PR (a
feattouching root files) will also make release-please propose an app0.9.0release PR alongside the chart'sxapi-lrs-chart/0.1.0; merge or ignore that one as desired.