Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Support reproducable deployments #299

Open
Tracked by #148
NickLarsenNZ opened this issue Jun 11, 2024 · 0 comments
Open
Tracked by #148

feat: Support reproducable deployments #299

NickLarsenNZ opened this issue Jun 11, 2024 · 0 comments

Comments

@NickLarsenNZ
Copy link
Member

NickLarsenNZ commented Jun 11, 2024

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant