Open huiwq1990 opened 11 months ago
Hi @huiwq1990, Thanks for opening an issue! We will look into it as soon as possible.
The apiserver can open the NodePort directly to provide external access, or you can access the clusterpedia apiserver service directly in the cluster.
Of course, you still need to add a prefix clusterpedia.io/v1beta1/resources
Adding paths without prefixes looks good, and in the future we might be able to add a gate to support it
What would you like to be added?
1)Export binding-apiserver as apiserver directly to user, the server path not need add lusterpedia.io/v1beta1/resources suffix; 2)clusterpedia-apiserver support service nodeport;
In a word, we want to use binding-apiserver like this:
The
binding-apiserve-ip
could beclusterpedia-apiserver
service ip or host cluster node ip. Thebinding-apiserve-port
could beclusterpedia-apiserver
service port or nodeport.Why is this needed?
In normal case, binding-apiserver works as a aggregated apiserver, and exposed by host apiserver. So all binding-apiserver requests must forward by host apiserver, and it effects host apiserver performance. In other case, we want to watch binding-apiserver, but after a while, we get some error.