Open jakubdyszkiewicz opened 2 years ago
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Description
pkg/api-server
tries to gather all the endpoints in one package. The result is that API Server takes a lot of dependencies and is very bloated.What we should do instead is what we've done with
pkg/dp-server
package. Which is to provide the backbone of api-server, but define and register the endpoints in a corresponding packages. For example:pkg/tokens
.pkg/inspect
(or something similar)As we are ramping up GUI work, I expect new APIs, which will make this problem worse. Testing is also much easier this way, because you don't need to build the whole API Server that now has dependency on MeshContextBuilder just to test
/config
.