commit | fe57c7509505ee1474ae19010d137d4f765d4825 | [log] [tgz] |
---|---|---|
author | kv <gxthrj@163.com> | Sun Jun 13 00:43:18 2021 +0800 |
committer | GitHub <noreply@github.com> | Sun Jun 13 00:43:18 2021 +0800 |
tree | b54937f36899e4624635d537cc85bd7d92f3dc21 | |
parent | b4e2e2a8aafd4ce2fdf6ff31fb52df66b881bca9 [diff] |
fix: use not strictly translation when remote ApisixRoute (#544) * fix: use not strictly translation when remote ApisixRoute * fix: lint & comments * add comments * fix: add upstreams to ctx when translation * use upstraemId instead of upstream in tcproute * fix: check upstream exist * test: add e2e test * CI: [Temporary changes]use APISIX:2.6 instead of APISIX:dev * use Apisix:dev image & use intstring type for counter * fix: counter * fix: use json.Unmarshal instead * fix: the count in cache should be modify too * recover test case * fix: style * fix: count compare * fix: style * fix: remove ginkgo focus test case
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.14+.
We welcome all kinds of contributions from the open-source community, individuals and partners.
#ApacheAPISIX