Publish release images for tagged releases

Open
#3,246 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, go, rust
Domain
devops, release

Research direction

Start with docs/operator-install.md and docs/examples/substrate-install.yaml to check the documented image repository and tag behavior, then inspect how ate-setup publish release-images builds and publishes images. Define the tagged release workflow for amd64 and arm64 and how image digests appear in release notes; done when each tag publishes both architectures and the documented image flags work.

Written by the indexing model from the issue text.

Description

area/dev-infra kind/bug

docs/operator-install.md and docs/examples/substrate-install.yaml use images.repo: ghcr.io/agent-substrate/substrate. But ghcr.io/agent-substrate/substrate/ateapi returns NAME_UNKNOWN, and the v0.6.0 release has no image assets.

So every user must run ate-setup publish release-images, which needs ko, Docker buildx and a Rust build of envoy-dataplane. Building the amd64 envoy-dataplane on an arm64 workstation takes a long time.

Request

Publish the release image set (amd64 and arm64) for each tag, with the digests in the release notes, so --image-repo and --image-tag work as the docs describe.

Dominant language
Go
Stars
5.9k
Forks
637
Avg merge
2d 1h
Merged PRs (30d)
523

Getting set up

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 agent-substrate/substrate

All issues in agent-substrate/substrate

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.