Most teams have adopted GitOps for deploying applications, yet many still rely on manual processes when promoting changes between environments.

Whether it’s service versions, configuration updates, platform settings, or operational artifacts, moving changes from development to production often involves custom scripts, spreadsheets, approval emails, and human intervention. These processes increase risk, reduce visibility, and make it difficult to answer a simple question: “What exactly changed, and how did it get here?”

In this session, I’ll share how we implemented Kargo to create repeatable promotion workflows across multiple environments, enabling teams to safely move changes from development to staging and production while maintaining Git as the source of truth.

We’ll explore how Kargo can be used for more than application deployments, including configuration promotion, service version management, environment synchronization, and operational change tracking.