Skip to content
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

Create permission for endpoints/restricted on OpenShift #280

Closed
tobru opened this issue Jan 7, 2022 · 3 comments
Closed

Create permission for endpoints/restricted on OpenShift #280

tobru opened this issue Jan 7, 2022 · 3 comments

Comments

@tobru
Copy link
Contributor

tobru commented Jan 7, 2022

The vcluster docs mention that create permission for the endpoints/restricted resource is required. On APPUiO Cloud we do not grant this permission to our restricted (normal) users. We're wondering why this permission is needed and if there is a way to circumvent this permission. Can you give us some insights on that requirement?

@matskiv
Copy link
Contributor

matskiv commented Jan 7, 2022

Hello @tobru
This permission is required because OpenShift has a built-in admission controller(some info about it is in this comment) for the Endpoint resources, which denies the creation of the endpoints pointing into the cluster network or service network CIDR ranges unless this additional permission is given. Vcluster needs to create endpoints pointing to the service CIDR range because it synchronizes Endpoints from a virtual cluster into a host cluster to ensure that the Services will work correctly.

It should be possible to achieve the correct Services functionality without the need for synchronization of all Endpoints, so I created this issue to investigate and implement the change - #281. Once it's done, the Endpoint synchronization would become optional, and we will put the endpoints permissions(including endpoints/restricted) into the "extended permissions" section of our chart(not required by default).

@tobru
Copy link
Contributor Author

tobru commented Jan 7, 2022

Thank you very much @matskiv for the explanation, that helps to understand it. I think we can close this issue, all is tracked in #281 👍

@matskiv
Copy link
Contributor

matskiv commented Jan 7, 2022

Cool, np. Okay, I'll close this one :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants