Using OpenAPI to configure your API Gateway
summary
Claims that OpenAPI can be the single source of truth for gateway config and that automation removes ops bottlenecks, demonstrated by cusk which generates ingress configs from OpenAPI for nginx ingress, Ambassador and Traefik and emits mappings, rate‑limit and timeout artifacts. cusk includes an x-cusk extension for rate limits, timeouts and CORS and a generator that targets each controller’s YAML/annotations. Kubeshop also ships cus-gateway built on Envoy to apply OpenAPI natively; the demo shows generated manifests applied to Kubernetes successfully.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:55Welcome
- 1:56Overview
- 3:20Recap
- 4:23OpenAPI Metadata
- 5:27One Source of Truth
- 8:24Common Approach
- 10:01OpenAPI Generator
- 10:57OpenAPI Gateway
- 14:53OpenAPI
- 15:06Kusk
- 15:50Kusk Extension
- 16:31Why use Kusk
- 17:23GitOps workflow
- 19:04Kubernetes demo
- 23:38Kubernetes Gateway
- 24:09Conclusion
related talks
26mStreamlining API Governance: Kubernetes Native API Management
29mBringing OpenAPI to devOps
24mLeveraging Gateway API for Kubernetes Native API Management
03h 18mHands-On with an Envoy API Gateway, Now with GraphQL!
28mBeyond Kubernetes Ingress (with Gateway API)
30mDesigning a Composable API Platform Powered by Open Standards
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking