the manger API should not listen 8080, which is the port of data plane

[moonming]

Bug report

https://github.com/apache/apisix-dashboard/blob/master/api/conf/conf.yaml#L21

Describe the bug

A clear and concise description of what the bug is.

How to Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Add screenshots to help explain your problem if applicable.

System information

• OS: [e.g. macOS, Windows]
• Browser (if applies) [e.g. Chrome, Safari, Edge]
• Version: [e.g. 2.0-rc3]

Additional context

Add any other context about the problem here.

[nic-chen]

@moonming
OK. What is the recommended port? 9081 or 8081? Thanks.

[moonming]

@gxthrj @membphis @spacewander @tokers what do you think about the port of CP?

[nic-chen]

ping @gxthrj @membphis @spacewander @tokers
request help, thanks.

[tokers]

@moonming Since the admin api port in DP will be changed to 9180 in version 3.0, what about using 9180 also?

[membphis]

We used port 9180 as CP in APISIX now, I think this is not a good port.

I prefer 9000 now. Here are the reasons:

1. The ports on the control plane and the data plane should be very different.
2. The port of the control plane allows the use of HTTP protocol or HTTPS protocol. So this port number avoids any protocol-related identification (such as 80 or 443).

[gxthrj]

But I think 80/ 443 is more accepted by the public, and the manager-api will be completely independent in 3.0, the port of CP and DP do not affect each other, so we can treat CP as an independent project.
When deploying independently, IP or domain names can be distinguished, so you no longer need to care about ports.

[nic-chen]

Through a meeting, it was finally determined that the default port of dashboard manager api will change to 9000.

Participants:
@gxthrj @membphis @spacewander @tokers @moonming @ShiningRush @nic-chen

will send a mail to our maillist.