Skip to content

docs: pin the shipped dashboard by release tag - #365

Merged
cplieger merged 1 commit into
mainfrom
feat/pin-dashboard-by-tag
Sep 18, 2026
Merged

cplieger merged 1 commit into
mainfrom
feat/pin-dashboard-by-tag

Conversation

@cplieger

Copy link
Copy Markdown
Owner

Summary

The dashboard ships with every release as a release asset (grafana-dashboard.json, its .sha256, a cosign bundle) and as an OCI artifact ghcr.io/cplieger/<repo>/dashboard:<tag>, so the README's dashboard section now says how to pin it the way the image is pinned: the release asset URL for grafana-operator spec.url, the Grafana Helm chart and Terraform, and the OCI reference for grafana-operator spec.oci, with a GrafanaDashboard snippet. The uid is stable, so a re-import updates in place.

Tested

markdownlint-cli2 with the fleet config: clean. The OCI artifact and the release assets referenced resolve for the current tag (anonymous GHCR manifest read and gh release view). Docs-only change, release-inert.

The dashboard ships with every release as a release asset and as an OCI
artifact at the app's tag, so the README's dashboard section says how to
pin it the way the image is pinned: the release asset URL for
grafana-operator spec.url, the Grafana Helm chart and Terraform, and the
OCI reference for grafana-operator spec.oci, with the uid kept stable so
a re-import updates in place.
@cplieger
cplieger merged commit 2d7ab05 into main Sep 18, 2026
19 checks passed
@cplieger
cplieger deleted the feat/pin-dashboard-by-tag branch September 18, 2026 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant