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

centraldashboard: kubeflow in a custom namespace instead of kubeflow namespace #7063

Closed
deepk2u opened this issue Mar 24, 2023 · 1 comment · Fixed by #7064
Closed

centraldashboard: kubeflow in a custom namespace instead of kubeflow namespace #7063

deepk2u opened this issue Mar 24, 2023 · 1 comment · Fixed by #7064
Assignees

Comments

@deepk2u
Copy link
Contributor

deepk2u commented Mar 24, 2023

/kind feature

Why you need this feature:
I am trying to install kubeflow in a namespace other than kubeflow. I am using the pipelines and notebooks module, everything else is working except centraldashboard.

looks like namespace is hardcoded as part of the code here:

private namespace = 'kubeflow';

there is an option to override namespace using kubeconfig and setting context here:

this.namespace = context.namespace;

But, in this case we would need to provide the kubeconfig, which is not posssible in all cases, because of security reasons.

Describe the solution you'd like:

  1. The idea is to make namespace variable value come from an environment variable.

  2. The other idea is to fetch the namespace from the serviceaccount token.

Both are valid solutions in my opinion.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@kubeflow-bot kubeflow-bot added this to To Do in Needs Triage Mar 24, 2023
@deepk2u deepk2u changed the title kubeflow in a custom namespace instead of kubeflow namespace centraldashboard: kubeflow in a custom namespace instead of kubeflow namespace Mar 24, 2023
@deepk2u
Copy link
Contributor Author

deepk2u commented Mar 25, 2023

/assign @kimwnasptd

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

Successfully merging a pull request may close this issue.

2 participants