Open trevorwhitney opened 2 weeks ago
@morganrowse if you're still interested, looks like the saga isn't quite over
Hi @trevorwhitney just got back from leave and now ready to look into this.
I have a theory that this CI issue was introduced by some upstream changes to grafana/helm-charts
shared github actions here, The grafana/loki
helm-release action makes use of the main
branch here, something akin to using latest
on a docker container.
It looks like the core issue here follows this PR https://github.com/grafana/helm-charts/pull/3418
@narqo just raising for visibility if you have not seen this for the Loki chart. Im not seeing any fundemental code differences between mimr and loki CI. Are there GitHub app or repo permission settings required to get this working as expected?
https://github.com/grafana/helm-charts/issues/3068#issuecomment-2473690415
Im not seeing any fundemental code differences between mimr and loki CI. Are there GitHub app or repo permission settings required to get this working as expected?
It should just work since https://github.com/grafana/helm-charts/pull/3424 — no special changes on your side needed (it works for k6-operator also).
@narqo we're referencing thew workflow @ main
but still seeing those 403 errors Error: unexpected status from POST request to https://ghcr.io/v2/grafana/helm-charts/loki/blobs/uploads/: 403 Forbidden
Awesome, thanks @morganrowse, I reverted the release pipeline to 70dbbb722dee3f2ee126e12684cc0e92a20972ed
before the ghcr
changes, and our release went out successfully this week. Going to keep this issue open until we fix it for real though, as we should bring back the ghcr
pushing.
14799 fixed the
helm-ci
action, allowing helm PRs to be merged. However, publishing releases is still broken:Last successful run was 3 weeks ago: https://github.com/grafana/loki/actions/runs/11374046600