Optimizing Resilience and Availability by Migrating from JupyterHub to Kubeflow Notebook Controller

Explore a detailed presentation on Capital One's migration from JupyterHub to the Kubeflow Notebook Controller, focusing on optimizing resilience and availability. Learn about the limitations of JupyterHub's backend-agnostic architecture in Kubernetes environments and discover how the Kubernetes-native Kubeflow Notebook Controller addresses these shortcomings. Gain insights into the benefits of adopting a truly Kubernetes-native solution, including reduced complexity, improved scalability, and enhanced user satisfaction. Understand how this transition enabled Capital One to support four times as many users and ten times more concurrent executions while reducing operational overhead for platform engineers.