Uploaded August 2026 | Updated September 2026, 2 weeks ago
Don't miss out! Join us at our next KubeCon + CloudNativeCon events in Shanghai, China (8-9 September, 2026) and Salt Lake City, United States (Nov 9–12, 2026). Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
The Evolution of GitOps in Platform Engineering - Artem Lajko, iits
GitOps in 2017 as a simple model for application delivery, built around four core principles. Today, it has evolved into a central part of platform engineering, where teams operate large numbers of clusters and shared platform services.
This talk shows how GitOps has evolved over time, why early approaches break at scale, and how everything-as-code enabled automation while also creating configuration sprawl. Tools like Argo CD, Helm, and Kustomize made scaling possible, but often hide the real state of a system.
We will look at the limits of Git as a state store and why file-based, pull-driven reconciliation does not scale well. This led to OCI-based delivery, Gitless GitOps, and new approaches that aim to provide a real, operable state store.
Platform teams need visibility, regulation like the Cyber Resilience Act requires a clear infrastructure supply chain, and AI-driven operations depend on access to the final, real manifests.
Don't miss out! Join us at our next KubeCon + CloudNativeCon events in Shanghai, China (8-9 September, 2026) and Salt Lake City, United States (Nov 9–12, 2026). Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
The Evolution of GitOps in Platform Engineering - Artem Lajko, iits
GitOps in 2017 as a simple model for application delivery, built around four core principles. Today, it has evolved into a central part of platform engineering, where teams operate large numbers of clusters and shared platform services.
This talk shows how GitOps has evolved over time, why early approaches break at scale, and how everything-as-code enabled automation while also creating configuration sprawl. Tools like Argo CD, Helm, and Kustomize made scaling possible, but often hide the real state of a system.
We will look at the limits of Git as a state store and why file-based, pull-driven reconciliation does not scale well. This led to OCI-based delivery, Gitless GitOps, and new approaches that aim to provide a real, operable state store.
Platform teams need visibility, regulation like the Cyber Resilience Act requires a clear infrastructure supply chain, and AI-driven operations depend on access to the final, real manifests.
