ingress controller for K8s

Clone this repo:
  1. f0ed89f chore: add check version script (#200) by rootlh · 14 hours ago master
  2. e1eb3e5 chore: introduce ingress-types, rename ApisixTls to ApisixTLS (#192) by Alex Zhang · 16 hours ago
  3. 009db9b add milestone link (#198) by rootlh · 20 hours ago
  4. 7cbd15f doc: Add Apache APISIX link in README (#194) by fukiki · 34 hours ago
  5. 75e7ff2 chore:add ginkgo check before e2e-test(apache #186) (#190) by yuntao.cao · 35 hours ago

Apache APISIX for Kubernetes

Go Report Card

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:

Status

This project is currently considered experimental.

Features

  • 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.

Modules

1. Ingress types Submodule

  • 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.

  • CRD design

2. APISIX types Submodule

  • 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.

3. Seven submodule

  • Contain main application logic.

  • Sync the k8s cluster states to Apache APISIX, based on Apisix-types object.

4.Ingress-controller Submodule

  • 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.

Get started

Todos

  • Support UDP definition. #116
  • Support TCP definition. #115
  • Support GRPC definition. #114
  • Add a complete demo. #9
  • More todos will display in issues

Documents

FAQ

User stories

Contributing

We welcome all kinds of contributions from the open-source community, individuals and partners.

Community

Milestone

Terminology

  • Ingress APISIX: the whole service that contains the proxy (Apache APISIX) and ingress controller (apisix ingress controller).
  • apisix-ingress-controller: the ingress controller component.

License

Apache License 2.0