Skip to content

Securing upstream releases #2490

@jotak

Description

@jotak

Upstream builds and releases are done through GitHub worklows:

  • Every push to main triggers an OCI image build, which is pushed to quay.io.
  • Releases are triggered by a git tag, and resulting images are pushed as well to quay.io.

The release process is described here. Some manual steps are involved to publish release notes and the Helm chart.

The on-push builds may remain as is, but we need to secure the release builds by:

  • Generating SBOM
  • Signing images
  • Making releases immutable
  • Automating the Helm chart generation (optional)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions