How have we applied GitOps to user permissions, configuration, and observability to build interior platforms
Learn about the Everything-as-a-Code approach from our experience to enable effective and successful collaboration between hundreds of engineers by the GitOps approach. I share how my squad and I married GitOps practices to build “permissions-“, “configuration-” and “observability-“ as-a-code services. I'll give you tips on how the strategy should be designed to aid you start with GitOps rapidly and build powerful interior platforms.
In Dynatrace, about 1,500 devs collaborate regular across multiple locations and time zones. Automation is key to supporting fast-paced innovation. We’ve started from a hackathon to build the first version of task Monaco (aka MONitoring As COde) – where we fundamentally automate observability as a code. Then, we realized we could apply the same approach to any area – for instance, by “permissions-as-a-code,” anyone and anytime can elevate their approval to access fresh services by submitting just a pull request, or by "configuration-as-a-code" we can enable DevOps teams to steer application's configuration easily.
How can I start with GitOps?
The most crucial enabler for GitOps is appropriate RESTful API. We’ll go through the most crucial guidelines on how API should be structured. Then, I will teach you what a basic GitOps workflow looks like. Finally, based on open origin task Monaco, we’ll learn that applying a state from the repository can be easy achievable.
I’m certain that after this session, many of you'll be inspired that your squad and possibly even platform users can unleash unprecedented power of automation and effectiveness.
DevOpsDays Warsaw: https://devopsdays.pl/
