commit | 70d010092b626c9c6959bd026e669dbb60153608 | [log] [tgz] |
---|---|---|
author | Fang <37891485+fhuzero@users.noreply.github.com> | Fri Jun 25 09:15:56 2021 +0800 |
committer | GitHub <noreply@github.com> | Fri Jun 25 09:15:56 2021 +0800 |
tree | 4cd2b7109a6d57d08d41df6b507e0ff4d1cfaeb5 | |
parent | 2122d76fd28cc7bce54e8f52e2d4c9d04a1e852a [diff] |
chore: update config of installation by Kustomize (#557) Update default values in config file to make the installation of apisix-ingress-controller by Kustomize ready to use. * update the default version of apisix-ingress-controller container image to keep it up-to-date * update apisix.base_url to send requests to the correct APISIX address * add apisix.admin_key to configure APISIX Admin API access token. This avoids 401 Authenticaion Required error when invoking APISIX Admin API
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