Open
Description
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.
- The commit hash of
- 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.