GitOps - The Bad and the Ugly
Over the last few years the GitOps approach found many advocates. There are many good reasons for adopting GitOps including its modular and tool-independent architecture. But it also comes with particular pain points. These are especially felt by bigger organizations with dozens or even hundreds of teams who are facing the limits of traceability, manageability.
Ádám Sándor, Cloud Architect at Container Solutions came up with an article about the limitations of GitOps, that was discussed intensively. In this round table discussion, we want to provide a forum to discuss pros and cons of the approach with the community, but also brainstorm alternative or additional solutions.
During this round table discussion with Ádám we will detail questions including:
- What are the main reasons to adopt GitOps?
- What are the limitations of GitOps?
- How to overcome those limitations?
After a 30 minutes round table discussion with Ádám Sándor and Chris Stephenson, CTO at Humanitec, there will be 15 minutes for a discussion with the audience. We’d like to encourage you to share your experience with GitOps or submit your questions in advance.
Audience - who should join?
DevOps Engineers, Site Reliability Engineers, System Engineers, Infrastructure Kubernetes Administrators, Technical Architects, Application Developers with an affinity with DevOps and Technical Management
GitOps - The Bad and the Ugly
Ádám is a Cloud Native Architect at Container Solutions, helping companies adopt Cloud Native tech. Coming from a Java-dev background he is most excited about the space where software development and operations meet. When he is not flying in DCS World he is hacking on CI/CD, GitOps and Kubernetes Operators.
