GitOps agents like Argo CD and Flux excel at maintaining your Kubernetes cluster’s desired state from Git. But they leave a critical question unanswered: how do you promote changes across environments?