-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APISIX Dashboard V3 Roadmap #2353
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Background
Apache APISIX has released a roadmap for version 3.0, and as a counterpart to this, I am also releasing the roadmap for the dashboard here. In the new dashboard, we will implement better compatibility with APISIX, simpler deployment methods, and will also improve issues that existed in the previous version.
Objectives
Easier to use, better experience.
Past problems
There are many problems for user.
And some for developer.
From now
We want to improve the problem in the new version, or at least part of them.
We will improve one of the root causes of the current complexity, the "Manager API", which makes some things complicated. When I learned that APISIX V3 will improve the Admin API, I learned that we can use it directly in Dashboard, in a proxy-based way. This is the most important change we have made in this version.
At the same time, we may also make changes to the project versioning system to better help users interface with APISIX (TBD).
Roadmap
Here are the features about what we are going to implement in this version and the features to be discussed. Only a rough description is provided here, no details about the implementation are available.
- remove complex storage layer implementations
- reduce overall complexity
- goal-oriented resource control
- more image of consumer and service control
- support full function UI configuration
- support for APISIX migration on upgrade
- store dashboard only data
dev
- Graphical design plugin flow
dev
- support add plugin on UI
- support generating forms for user-defined plugins
- API specification for secondary development
dev
- supports configuration of multiple Admin API endpoints + token
- record old version data and support setting back
Other
If you have any suggestions or questions about this, you can communicate them in a discussion thread or mailing list that will be started later.
The text was updated successfully, but these errors were encountered: