The Ingress API has existed as beta type since early 2016 release in Kubernetes 1.2. Since its inception, it has been fairly lightweight and additions remained infrequent in attempts to maintain portability within the Kubernetes ecosystem. In response, Ingress API implementations commonly leverage a different internal API or extend the Ingress API by heavily decorating the resource with annotations.
In this session, we will present the Ingress enhancements for the GA/v1 Ingress API and what factors went into these decisions. Furthermore, we'll explore several possible directions for what a v2 API could entail and walk through several examples including existing non-Kubernetes implementations
Thursday November 21, 2019 3:20pm - 3:55pm
Room 16AB - San Diego Convention Center Mezzanine Level
Customizing + Extending Kubernetes
Experience Level Intermediate (Mid-level experience)
Session Slides Included Yes