[STORY] Release pages with install, upgrade and verify steps; signed OCI chart; Scorecard; pinned kind

Open
#2,419 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, github-actions, go, helm, kubernetes
Domain
ci-cd, release

Research direction

Start with .github/workflows/release-please.yml and the e2e workflows test-e2e.yml and test-e2e-rbac.yml; inspect how release bodies and chart pushes are handled. Add the Scorecard workflow and pin kind as described in the scope. Run actionlint .github/workflows/*.yml and verify the chart with the documented cosign verify command; done when release jobs reject missing footers or unsigned chart pushes.

Written by the indexing model from the issue text.

Description

ci enhancement priority/medium size/medium

Goal

Make each release page tell a user how to install, upgrade and verify that release, and close the remaining supply-chain gaps that a reviewer checks first.

Definition of done

  • Observable: every release body ends with an install and upgrade block (helm install ... --version <v>, brew upgrade), the gh attestation verify command, and the image digests; the OCI Helm chart is cosign-signed; an OpenSSF Scorecard workflow runs on main; kind is pinned in the e2e workflows.
  • Negative: a release body without the footer, or an unsigned chart push, fails the release job.

Scope

  • .github/workflows/release-please.yml (release body footer, chart signing), a Scorecard workflow, test-e2e.yml and test-e2e-rbac.yml (pin kind).

Out of scope

  • The tool pinning and verification-identity changes in #2398.

Consumers and surfaces touched

  • GitHub release bodies, the OCI chart in ghcr.io/defilantech/charts/llmkube, CI workflows.

Verification

actionlint .github/workflows/*.yml
cosign verify ghcr.io/defilantech/charts/llmkube:<v> --certificate-identity <main release workflow> --certificate-oidc-issuer https://token.actions.githubusercontent.com

Falsification

  • Edit: drop the chart signing step.
  • Expected failure: the documented cosign verify for the chart fails on the next release.

Risks

  • Scorecard findings will need triage; start it as informational.
Dominant language
Go
Stars
232
Forks
37
Avg merge
21h 42m
Merged PRs (30d)
244

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defilantech/LLMKube

All issues in defilantech/LLMKube

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.