Huge thanks to our host Mobileye, and event sponsor TeraSky.
📣 Calling all cloud native enthusiasts in the Jerusalem area!
We are excited to be coming back with the CNCF Jerusalem meetup!
Join Scott Rosenberg, Ben Hirschberg, Sharone Zitzman and the entire CNCF Jerusalem and cloud native community for a fantastic event.
About this event
We are extremely excited to be coming back with a new event for our Jerusalem Kubernetes and Cloud Native enthusiasts!
Stay tuned for the fantastic talks as they're announced, and be sure to help us spread the word - we'd love to see as many folks as possible join our event!
Opening words by our hosts Mobileye, Sefi Darshan - Mobileye
Mobileye welcome and opening words
3:15 PM
Your K8s Infinity Gauntlet: The Marvel of KEDA and Cluster-API for Infinite Scale, Scott Rosenberg, Lead Architect, CTO Office - TeraSky
One of the greatest out of the box features of Kubernetes is its auto-scaling capabilities, which has a naive implementation or more advanced scheduling capabilities through native tooling. However, both of these models are reactive and not proactive in nature. What if we could employ proactive event-driven scaling of our clusters?!
Over our many years of cloud native operations at scale, with the right tools we could! Enter KEDA (AKA Kubernetes Event-Driven Autoscaling). KEDA was built to make just this type of intelligent auto-scaling possible - this includes everything from event-driven and predictable actions like scaling up and down for predictable bursts of usage or shutting down dev clusters during specific and non-working hours, to managing scaling based on your workloads and message queues, or even your APMs and based on the metrics it ingests. In this talk we’ll walk through auto-scaling on steroids with KEDA, how it can be supercharged through CRDs, and in particular the cluster-API which now makes it possible to provision, update, customize and delete K8s clusters declaratively––that together are a gamechanger when it comes to the infinite scale K8s makes possible.
3:45 PM
Kubernetes-Native Workflows: Why We Chose Argo Workflows Over Cloud Serverless, Chai Tadmor, Root.io
When building workflow-driven applications, you have several compelling options: you could go all-in on cloud serverless with AWS Step Functions and Lambda or adopt proven workflow engines like
Airflow or Temporal. But what if you want more control, better integration with your existing infrastructure, and the power to scale workflows like any other application? That's why we chose to go Kubernetes-native with Argo Workflows—and we're
ready to share what we've learned.
When we needed to scale our application and transition from a synchronous monolith to a background-workflow oriented architecture, we faced a critical decision. Instead of going the serverless route, we chose Argo Workflows on EKS to avoid Lambda's
execution limits, cold starts, vendor lock-in, and the extra complexity of managing workflows outside your GitOps workflows. By adopting Argo Workflows, we now run workflows as first-class Kubernetes applications. The result: full resource control
without Lambda's limitations, unified GitOps for workflows and infra, consistent patterns across dev, staging, and production, and native integration with the rest of our Kubernetes stack—including Karpenter for autoscaling, service mesh, and
advanced monitoring.
You'll see real production workflow examples, how GitOps principles shape our workflow management, and how we optimize resource usage to balance cost and performance. We'll cover our multi-environment strategies and show when Kubernetes-native
workflows make sense (and when they don't). If you're rethinking your orchestration approach—or just curious how far Argo Workflows can go—this talk will help you decide if it's time to bring your workflows closer to your cluster.
