WEBVTT

00:00.080 --> 00:02.799
Your ArgoCD is running, and yet every

00:02.799 --> 00:04.639
new team needs two weeks of onboarding

00:04.639 --> 00:06.581
before their first deployment goes through properly.

00:06.750 --> 00:07.549
I'm Clemens,

00:07.549 --> 00:08.750
founder of Cheveo.

00:08.750 --> 00:10.949
We build GitOps infrastructures for

00:10.949 --> 00:12.990
platform teams at DAX corporations.

00:12.990 --> 00:14.589
No theory workshop —

00:14.750 --> 00:16.589
we show you the exact setup

00:16.589 --> 00:17.992
that runs in production at our clients.

00:17.992 --> 00:20.249
In one day, you'll build a GitOps

00:20.249 --> 00:20.649
pipeline with us

00:20.649 --> 00:21.609
that onboards new teams via

00:21.929 --> 00:23.048
self-service,

00:23.048 --> 00:25.089
without anyone from your platform team

00:25.089 --> 00:25.703
having to step in.

00:25.702 --> 00:28.080
You'll walk away with an ApplicationSet pattern

00:28.080 --> 00:29.881
that scales with your clusters,

00:30.041 --> 00:31.960
a secrets and RBAC structure

00:31.960 --> 00:34.600
that survives an audit, and a repo

00:34.600 --> 00:36.360
you can reuse on Monday.

00:36.453 --> 00:38.133
This workshop isn't for Kubernetes

00:38.133 --> 00:38.612
beginners.

00:38.612 --> 00:39.332
It's for teams

00:39.332 --> 00:41.733
already using the GitOps pattern who

00:41.733 --> 00:43.173
finally want to scale it properly.
