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

Why are cluster administrator permissions required to install via Kubernetes? #2646

Open
tpanza opened this issue Dec 1, 2022 · 2 comments

Comments

@tpanza
Copy link

tpanza commented Dec 1, 2022

Hello,

I am trying to install MLRun onto a shared corporate Kubernetes cluster. The prereqs state the following:

Access to a Kubernetes cluster. You must have administrator permissions in order to install MLRun on your cluster.

Where can I learn more about why exactly admin permissions are required?

Might there be some alternative to this? For example, is there a way to separate the installation process into steps requiring admin and steps that do not, and then I could submit a request to the cluster administrators to run those admin-requiring steps for me?

Since the cluster I am trying to use is shared across a large corporate enterprise, the owners/admins are leery about installing products requiring admin permissions.

@liranbg
Copy link
Member

liranbg commented Dec 1, 2022

Hi @tpanza - to install resources that are cluster-wide such as CRDs it is required to have admin permissions. Nuclio helm chart is publicly so you can revisit and see what is being installed. https://github.com/v3io/helm-charts/tree/development/stable/mlrun

@tpanza
Copy link
Author

tpanza commented Feb 1, 2023

Thanks for the info @liranbg . Is there a way to split the installation process into two parts? Ex: First for an admin user to create the cluster-wide resources such as CRDs, then for a regular user to do the rest? What would that look like?

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

No branches or pull requests

2 participants