commit | 91d985edca67493acc22536c66d4947fe597052f | [log] [tgz] |
---|---|---|
author | chen zhuo <chzhuo@126.com> | Fri Aug 13 14:05:21 2021 +0800 |
committer | GitHub <noreply@github.com> | Fri Aug 13 14:05:21 2021 +0800 |
tree | 381f064717bb735de818e50ac52c563319d4659f | |
parent | f78248a6aca0ac4754fd4d5d410c28f1cdd3d9c7 [diff] |
fix field tag omiteempty (#622) Co-authored-by: zhuo.chen <zhuo.chen@upai.com>
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 general availability.
v1
and v1beta1
) support.More about comparison among multiple Ingress Controllers.
Apisix ingress controller requires Kubernetes version 1.15+. From the version 1.0.0, APISIX-ingress-controller need to work with Apache APISIX version 2.7+.
We welcome all kinds of contributions from the open-source community, individuals and partners.
#ApacheAPISIX