kubernetes-sigs/kubespray

Publish a collection artifact

Open

#12,731 opened on Nov 20, 2025

View on GitHub
 (17 comments) (0 reactions) (1 assignee)HTML (4,419 forks)batch import
help wantedkind/feature

Repository metrics

Stars
 (10,380 stars)
PR merge metrics
 (Avg merge 25d) (26 merged PRs in 30d)

Description

/kind feature

We need to publish somewhere a collection artifacts for our releases.

This should be automated as much as possible, given the already manual release process.

Possible automation source:

  • prow post-submits (see kubernetes/test-infra)
  • github workflows
  • gitlab-ci -> not sure if viable

Possible place to upload the artefact (at least once initially, multiple could be possible):

  • Ansible galaxy (pro: integration with the wider ansible ecosystem, cons: probably more work)
  • github releases

Not needed for a start but nice to have:

  • sign the artifacts, using sigstore -> via k/test-infra ? Not sure how artificat signing / promotion works for project under k-sigs, but I'd rather avoid handling keys ourselves if we can delegate to a trusted build service.

Contributor guide

Research direction
Investigate the current release process and choose an automation source (e.g., GitHub Actions) to publish collection artifacts to GitHub releases and optionally Ansible Galaxy.
Tech stack
python
Domain
devopsci cdinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCI/CDAnsible
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70