Apache APISIX is a dynamic, real-time, high-performance API Gateway.
APISIX API Gateway provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more.
You can use APISIX API Gateway to handle traditional north-south traffic, as well as east-west traffic between services. At present, APISIX has been used in various industries, including NASA, Tencent Cloud, EU Digital Factory, Airbus, Airwallex, iQIYI, etc.
Apache APISIX supports stand-alone mode and also supports the use of etcd database as the configuration center.
In stand-alone mode, APISIX uses apisix.yaml as the configuration center to store routing, upstream, consumer and other information. After APISIX is started, it will load the apisix.yaml file regularly to update the corresponding configuration information.
You can start an APISIX container with stand-alone mode by the following command:
shelldocker run -d --name apache-apisix \ -p 9080:9080 \ -e APISIX_STAND_ALONE=true \ apache/apisix
Add Route and Plugin configuration to the running APISIX container:
shelldocker exec -i apache-apisix sh -c 'cat > /usr/local/apisix/conf/apisix.yaml <<_EOC_ routes: - id: httpbin uri: /* upstream: nodes: "httpbin.org": 1 type: roundrobin plugin_config_id: 1 plugin_configs: - id: 1 plugins: response-rewrite: body: "Hello APISIX\n" desc: "response-rewrite" #END _EOC_'
Test example:
shellcurl [***]
shellHello APISIX
If you want to know more configuration examples, you can refer to stand-alone.
The operation of APISIX also supports the use of etcd as the configuration center. Before starting the APISIX container, we need to start the etcd container with the following command, and specify the network used by the container as the host network. Make sure that all the required ports (default: 9080, 9443 and 2379) are available and not used by other system processes.
shelldocker run -d \ --name etcd \ --net host \ -e ALLOW_NONE_AUTHENTICATION=yes \ -e ETCD_ADVERTISE_CLIENT_URLS=[***] \ bitnami/etcd:latest
shelldocker run -d \ --name apache-apisix \ --net host \ apache/apisix
Before starting the APISIX container, we need to create a Docker virtual network and start the etcd container.
shelldocker network create apisix-network --driver bridge && \ docker network inspect -v apisix-network && \ docker run -d --name etcd \ --network apisix-network \ -p 2379:2379 \ -p 2380:2380 \ -e ALLOW_NONE_AUTHENTICATION=yes \ -e ETCD_ADVERTISE_CLIENT_URLS=[***] \ bitnami/etcd:latest
subnet address. Create a APISIX configuration file in the current directory. You need to set allow_admin to the subnet address obtained in step1.shellcat << EOF > $(pwd)/config.yaml deployment: role: traditional role_traditional: config_provider: etcd admin: allow_admin: - 0.0.0.0/0 # Please set it to the subnet address you obtained. # If not set, by default all IP access is allowed. etcd: host: - "[***]" prefix: "/apisix" timeout: 30 EOF
shelldocker run -d --name apache-apisix \ --network apisix-network \ -p 9080:9080 \ -p 9180:9180 \ -v $(pwd)/config.yaml:/usr/local/apisix/conf/config.yaml \ apache/apisix
Check that APISIX is running properly by running the following command on the host.
curl "[***]" \ -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1'
The response indicates that apisix is running successfully:
json{ "total": 0, "list": [] }
If you want to modify the default configuration of APISIX, you can use the following command to enter the APISIX container and modify the configuration file ./conf/config.yaml, which will take effect after reloading APISIX. For details, please refer to ./conf/config-default.yaml.
docker exec -it apache-apisix bash
For more information, you can refer to the APISIX Website and APISIX Documentation. If you encounter problems during use, you can ask for help through slack and the mailing list.
If you change your custom configuration, you can reload APISIX (without downtime) by issuing.
docker exec -it apache-apisix apisix reload
This will run the apisix reload command in your container.
During the deployment process, in addition to the above operations, APISIX also derived the apisix-ingress-controller, which can be deployed and used in the K8s environment more conveniently.
Licensed under the Apache License, Version 2.0: [***]
来自真实用户的反馈,见证轩辕镜像的优质服务
免费版仅支持 Docker Hub 加速,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
免费版仅支持 docker.io;专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像加速服务
在 Docker Desktop 配置镜像加速
Docker Compose 项目配置加速
Kubernetes 集群配置 Containerd
在宝塔面板一键配置镜像加速
Synology 群晖 NAS 配置加速
飞牛 fnOS 系统配置镜像加速
极空间 NAS 系统配置加速服务
爱快 iKuai 路由系统配置加速
绿联 NAS 系统配置镜像加速
QNAP 威联通 NAS 配置加速
Podman 容器引擎配置加速
HPC 科学计算容器配置加速
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名加速
需要其他帮助?请查看我们的 常见问题 或 官方QQ群: 13763429