Convincing product teams to adopt GitOps in a large org

Is it practical to govern different teams in an organization to adhere to the same infrastructure automation model, or is it overengineering? Does a product team love managing infrastructure besides shipping features, or does it feel overwhelmed? From an organizational perspective, how complex is it to drive change and convince teams to adopt a well-established concept like GitOps?

In some teams, bigger concerns include:
• No audit trail
• Less transparency
• Lack of infrastructure visibility
• No predictable state in case of disaster recovery
• No best practices followed

During a shift from software engineer to system engineer, the speaker gathered broad experience moving from 'asking support' to 'giving support' to product teams in adopting GitOps.

Takeaways:
• Successfully implementing GitOps
• Filling the infrastructure knowledge gap
• Using IaC and understanding predictable systems
• Meeting deadline after deadline