-
Notifications
You must be signed in to change notification settings - Fork 122
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
Expose binding-apiserver directly to end uses #589
Comments
Hi @huiwq1990, DetailsInstructions for interacting with me using comments are available here. |
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 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.The
binding-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.
The text was updated successfully, but these errors were encountered: