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

Labels added to namespace object while KF profile creation persistent even after deleting profile #2891

Open
PoornimaDevii opened this issue Mar 30, 2022 · 2 comments
Labels

Comments

@PoornimaDevii
Copy link

PoornimaDevii commented Mar 30, 2022

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
In a KF installed environment, it is specifically required that namespace is created initially, post which KF profile is created. Required namespace-labels such as pipelines.kubeflow.org/enabled: "true", serving.kubeflow.org/inferenceservice: enabled, etc are added to the corresponding namespace object, on creating the profile. But on deletion of the profile, the profile controller fails to erase/remove those labels from the namespace object.

P.S. It is known that the KF profile is the parent object which spins out a namespace usually, but in my case, its necessary to do first create a namespace and then later profile.

What did you expect to happen:
The labels which were added to namespace object on profile creation, needs to be reversed/removed on profile deletion.

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

Environment:

  • Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): v1.4
  • Kustomize version : 3.4.0
  • Kubernetes platform: (e.g. minikube) EKS
  • Kubernetes version: (use kubectl version): 1.19
  • OS (e.g. from /etc/os-release): Ubuntu 18.04.3 LTS
@PoornimaDevii
Copy link
Author

@andreyvelich

@biswajit-9776
Copy link
Contributor

/transfer manifests

@google-oss-prow google-oss-prow bot transferred this issue from kubeflow/kubeflow Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants