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

Discuss deployment in non-kubeflow namespace #698

Open
NohaIhab opened this issue Sep 13, 2023 · 0 comments
Open

Discuss deployment in non-kubeflow namespace #698

NohaIhab opened this issue Sep 13, 2023 · 0 comments
Labels
enhancement New feature or request Kubeflow 1.8 This issue affects the Charmed Kubeflow 1.8 release

Comments

@NohaIhab
Copy link
Contributor

NohaIhab commented Sep 13, 2023

Description

There's a new environment variable added in kubeflow dashboard called POD_NAMESPACE
this env variable enables the dashboard to be deployed in any namespace, not just kubeflow like it was hardcoded in the past, see this change.
The same is applicable for kfp, see this change.
We need to discuss whether we should support deployment in a namespace other than kubeflow, now that it seems to be unblocked by upstream, and whether it will be part of the 1.8 release.

@DnPlas suggested that in order to take on this effort, we need to:

  • ensure all kubeflow components can now be deployed in any namespace
  • remove the namespace check in some of our charms
  • remove the hardcoded namespace in our templates and/or charm code (if any)
@NohaIhab NohaIhab added the enhancement New feature or request label Sep 13, 2023
@NohaIhab NohaIhab added the Kubeflow 1.8 This issue affects the Charmed Kubeflow 1.8 release label Sep 13, 2023
This was referenced Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Kubeflow 1.8 This issue affects the Charmed Kubeflow 1.8 release
Projects
Status: Needs discussion
Development

No branches or pull requests

1 participant