KubeDay Australia 2024

There are many use cases for scheduling in the world, and the maintainers regard extendability as crucial. Kube-scheduler has two major ways to extend it, webhook and Go SDK. However, these come with drawbacks; performance/extendability issues with webhook, and the need to rebuild and replace schedulers with Go SDK. The proposed talk seeks to introduce our new solution to these challenges - a WebAssembly based extension. We’ll begin with a story about why custom schedulers are needed, and how existing extensions work. Then, we’ll get into why architecturally WebAssembly is a great fit for plugins, while also covering its challenges, such as sandbox limitations and programming concerns. This session will be delivered by Kensei, SIG-Scheduling core maintainer who founded the wasm extension. When you leave this session, you will know first-hand how a complex WebAssembly project looks and feels, with concrete details of how WebAssembly fits into infrastructure extensibility in general.

As organizations attempt to build internal developer platform s to standardize the way they deploy and manage cloud-native applications, they struggle with the cost and complexity of building and operating a home-grown solution. Radius is an open-source framework that enables developers and operators to build, deploy and operate on cloud native applications across public and private clouds. In this session, I'll talk about why developers and operators might want to use Radius when building cloud-native applications, go into the architecture of Radius, compare it other common tools and frameworks for managing cloud native apps, and show how you can build cloud-native applications using Radius. By the end of this session, you'll have an understanding of what Radius is and how you can use it to build and manage your cloud native apps.

As organizations scale their cloud adoption, they continue to find bottlenecks in their ability to deploy new workloads due to the shear number of resources centralized teams must manage. Developers at these organizations must traverse through multiple workflows—stitching together outputs from multiple pipelines—to deploy their applications. These delays result in new workloads or features taking up to 6-12 months to launch into production. Attempting to remove the bottleneck of centralized teams and empower developers, technical leadership is driving self-service automation initiatives commonly referred to as platform engineering. This presentation covers why platform engineering is trending, why new tools and methodologies are required, real-world customer use-cases, and how to get started. Additionally we’ll demo how to build a modern platform using OSS CNCF tools like Argo, Crossplane, and Gatekeeper.