Simpler and more flexible Kubernetes Ingress: Apache APISIX
summary
Apache APISIX Ingress implements Apache APISIX as a Kubernetes ingress controller, syncing Ingress and CRDs to an APISIX cluster via admin APIs and running in production for many enterprises; it claims declarative configuration with no reload on change, supports 70+ official plugins, traffic split, service discovery and health checks, and can be deployed co-located or as a central APISIX cluster managing multiple Kubernetes clusters; versions reached GA in June 2021 and v1.4 is current with v1.5 planned.
AI-written summary · about
chapters (10)
- 0:00Apache APISIX Ingress intro
- 1:28What is APISIX Ingress
- 3:13How APISIX Ingress works
- 4:17Key features
- 5:01Project timeline
- 6:06Why choose APISIX
- 7:55Scalability with plugins
- 8:57Flexible architecture
- 10:22Production feedback
- 10:43Future plans
related talks
24mA Hands-On Introduction to the Kubernetes Gateway API with Apache APISIX
29mKubernetes Ingress Controller with Apache Traffic Server [I]
49mAdvanced Ingress for Your Kubernetes Apps
20mInside Kubernetes Ingress
34mBack to Basics, Getting Traffic Into your Kubernetes Cluster
25mKubernetes Ingress: Do More with Less
21mCentralized Authentication with Apache APISIX and Ory
28mBeyond Kubernetes Ingress (with Gateway API)
