Главная
Study mode:
on
1
Introduction
2
Who am I
3
Back to Twitter
4
Why use crds
5
Cost of crds
6
Research
7
Current State
8
Goal
9
Existing tooling
10
CRDbased tooling
11
Why not just use the underlying libraries
12
Standalone use case
13
GitHub organization
14
BadIdea repository
15
Dependencies
16
Application Overview
17
Rest Configuration
18
Controller Manager
19
Cubeconfig
20
Creating a Resource
21
Whats Missing
Description:
Explore the process of creating an embeddable Kubernetes-style API server with Custom Resource Definition (CRD) support in this 25-minute conference talk from KubeCon + CloudNativeCon North America 2021. Dive into Jason DeTiberus' journey of building a minimal API server that removes the Kubernetes cluster dependency while maintaining CRD functionality. Learn about the challenges, research, and implementation details involved in piecing together components used by Kubernetes to support CRDs. Gain insights into the project's current state, goals, and existing tooling comparisons. Discover the structure of the "BadIdea" repository, including its dependencies, application overview, and key components such as REST configuration and controller manager. Understand the process of creating resources and identify areas for further development in this innovative approach to Kubernetes-style API servers.

From Tweet to BadIdea - Creating an Embeddable Kubernetes Style API Server

CNCF [Cloud Native Computing Foundation]
Add to list
0:00 / 0:00