Engin Diri
As a Senior Solutions Architect at Pulumi with over 15 years of experience in the IT industry, including roles at the Schwarz Group and W&W Versicherungen, I bring extensive expertise with an end-user and enterprise focus. Currently working for a startup while collaborating with enterprise clients has further enriched my experience!
I began my career as a Java backend developer, transitioned to frontend development, and ultimately specialized in CI/CD and DevOps. Working with ANT and Cruise Control to switch to Jenkins and Microsoft Team Foundation Server added some traumas on top! But as they say, what doesn't kill you makes you stronger.
I have now embraced the dynamic world of DevOps and Platform Engineering, leveraging cloud technologies and Kubernetes.
Recently, I have been exploring AI to find ways to make myself redundant in the future.
Session
Kube Resource Orchestrator (kro) has been steadily gaining traction as a Kubernetes-native way to build higher-level abstractions for platform engineering. Kro enables platform teams to create Platform APIs that bundle multiple Kubernetes and cloud resources into a single, self-service interface.
At its core, kro uses a ResourceGraphDefinition to define the components, their dependencies, and how they should be deployed. This eliminates sprawling YAML files, automates ordering, and lets application teams consume infrastructure without wrestling with raw Kubernetes manifests.
In this lightning talk, I’ll show:
- What a Platform API built with kro looks like.
- How it compares to tools like Crossplane compositions and Helm.
- Where kro fits in your platform engineering roadmap.
In just 5 minutes, you’ll see how this approach can make your platform APIs higher-level—and your delivery pipelines faster.