| commit | f494919694d0a371219f223042f18494f164adbb | [log] [tgz] |
|---|---|---|
| author | Baoyuan <baoyuan.top@gmail.com> | Sat Jan 28 17:53:07 2023 +0800 |
| committer | GitHub <noreply@github.com> | Sat Jan 28 17:53:07 2023 +0800 |
| tree | 8d715c6279b85d979f339aff846c5c4f6dca9de0 | |
| parent | 7ce75b9b1b561d51f1de921447b322e7ee20bac3 [diff] |
feat: release 3.0.0 (#2722)
The master version should be used with Apache APISIX master version.
The latest released version is 3.0.0 and is compatible with Apache APISIX 3.0.x.
The Apache APISIX Dashboard is designed to make it as easy as possible for users to operate Apache APISIX through a frontend interface.
The Dashboard is the control plane and performs all parameter checks; Apache APISIX mixes data and control planes and will evolve to a pure data plane.
Note: Currently the Dashboard does not have complete coverage of Apache APISIX features, visit here to view the milestones.
Username: admin Password: admin
Currently, APISIX Ingress Controller automatically manipulates some APISIX resources, which is not very compatible with APISIX Dashboard. In addition, users should not modify resources labeled managed-by: apisix-ingress-controllers via APISIX Dashboard.
. ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── Dockerfile ├── LICENSE ├── Makefile ├── NOTICE ├── README.md ├── api ├── docs ├── licenses └── web
api directory is used to store the Manager API source codes, which is used to manage etcd and provide APIs to the frontend interface.web directory is used to store the frontend source codes.Support the following ways currently.
Pull requests are encouraged and always welcome. Pick an issue and help us out!
Please refer to the Development Guide.
Please refer to the User Guide.
Please refer to the Contribution Guide for a more detailed information.
Please refer to the FAQ for more known issues.