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

Installing Kubeflow in any custom namespace #5647

Closed
deepk2u opened this issue Feb 28, 2021 · 4 comments
Closed

Installing Kubeflow in any custom namespace #5647

deepk2u opened this issue Feb 28, 2021 · 4 comments

Comments

@deepk2u
Copy link
Contributor

deepk2u commented Feb 28, 2021

/kind feature

Why you need this feature:
Kubeflow seems to be very tied with the namespace name kubeflow, ideally, it should be customizable and we should be able to install in any named namespace

Describe the solution you'd like:
Parameterize all the namespace related variables

Anything else you would like to add:

@jbottum
Copy link
Contributor

jbottum commented Mar 9, 2021

/priority p2
/area installation

@jbottum
Copy link
Contributor

jbottum commented Mar 9, 2021

@deepk2u thanks for your suggestion. I suspect this would be a helpful option for enterprise and on-prem users. If you need this for on-prem, you might bring it up in the next on-prem SIG meeting, https://docs.google.com/document/d/1Qs94d9RPxqiZJnTRvL9iHZrx_jnf59HyJFnbyi1AYjQ/edit#heading=h.w4esj4yrc6i

@stale
Copy link

stale bot commented Jun 9, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale label Jun 9, 2021
@stale stale bot closed this as completed Jun 23, 2021
@themowski
Copy link

I think that this would be useful for anyone who wants to run multiple versions of Kubeflow in the same cluster -- the use-case would be helping with an upgrade to a new version of Kubeflow. Conceptually, you could have an older version of Kubeflow running that users are actively using, and then deploy a newer version to a fresh namespace. Once it's running, users could be instructed to transition to that new instance once their jobs finish in the old one, and when everyone is out, the old one could be uninstalled.

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

5 participants