Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: Support reproducable deployments

Open
#299 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes, rust

Research direction

No files, tests, or specific entry points are named. Start by mapping where stackablectl builds Kubernetes manifests and handles deployment parameters, then define how commit and parameter metadata would be stored and used to reproduce an install on another cluster.

Written by the indexing model from the issue text.

Description

refinement-needed

Given an existing deployment in Kubernetes, it should be possible to reproduce that install on another Kubernetes cluster.

Ideas:

  • Store the stacablectl commit hash in the binary
  • Add labels to all deployed manifests with:
    • The commit hash of stackablectl to differentiate behaviours between versions.
    • Any CLI parameters that influence the content of the manifests.
  • Optional: CR/ConfigMap to track this stuff in Kubernetes so we don't need to rely on so many labels, then one label can refer to that CR/ConfigMap.
Dominant language
Rust
Stars
10
Forks
5
Avg merge
4h 41m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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 stackabletech/stackablectl

All issues in stackabletech/stackablectl

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.