Use Apache APISIX for Kubernetes Ingress
All configurations in apisix-ingress-controller are defined with Kubernetes CRDs (Custom Resource Definitions). Such as configure plugins, Support service registration discovery mechanism for upstreams, load balancing and more in Apache APISIX.
apisix-ingress-controller is an Apache APISIX control plane component. Currently it serves for Kubernetes clusters. In the future, we plan to separate the submodule to adapt to more deployment modes, such as virtual machine clusters.
The technical architecture of apisix-ingress-controller:
This project is currently considered experimental.
- Declarative configuration for Apache APISIX with Custom Resource Definitions(CRDs), using k8s yaml struct with minimum learning curve.
- Hot-reload during yaml apply.
- Auto register k8s endpoint to upstream(Apache APISIX) node.
- Out of box support for node health check.
- Support load balancing based on pod (upstream nodes).
- Plug-in extension supports hot configuration and immediate effect.
- Ingress controller itself as a pluggable hot-reload component.
- Multi-cluster configuration distribution.
-
Define the CRD(CustomResourceDefinition) needed by Apache APISIX
-
Currently supports ApisixRoute/ApisixService/ApisixUpstream，and other service and route level plugins.
-
Can be packaged as a stand-alone binary, keep in sync with the ingress definition.
-
Define interface objects to match concepts from Apache APISIX like route, service, upstream, and plugin.
-
Can be a packaged as a stand-alone binary, need to match with compatible Apache APISIX version.
-
Add new types to this module to support new features.
-
Contain main application logic.
-
Sync the k8s cluster states to Apache APISIX, based on Apisix-types object.
-
Driver process for ingress controller, watches k8s apiserver.
-
Match and covert Apisix-ingress-types to Apisix-types before handing the control over to the above module
seven.
Get more implementation details.
- Support
ApisixSSLCRD and the logic. #52 - Support retry when synchronization. #59
- Add a complete demo. #9
- Use terratest for testing with Kubernetes. #51
- More todos will display in issues
- aispeech: Why we create a new k8s ingress controller?(Chinese)
- Tencent Cloud: Why choose Apache APISIX to implement the k8s ingress controller?(Chinese)
We welcome all kinds of contributions from the open-source community, individuals and partners.
- Mailing List: Mail to dev-subscribe@apisix.apache.org, follow the reply to subscribe the mailing list.
- QQ Group - 578997126
- follow and interact with us using hashtag
#ApacheAPISIX- Bilibili video
