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

Can not find experiments in frontend if namespace is not kubeflow #774

Closed
Jeffwan opened this issue Sep 18, 2019 · 16 comments
Closed

Can not find experiments in frontend if namespace is not kubeflow #774

Jeffwan opened this issue Sep 18, 2019 · 16 comments

Comments

@Jeffwan
Copy link
Member

Jeffwan commented Sep 18, 2019

/kind bug

What steps did you take and what happened:
I am new to katib and not sure if this is an issue.

Based on my finding, I notice if I submit experiments in different namespaces other than kubeflow. There're two problems

  1. Can not find experiments on UI
  2. Sometimes experiment never get done. Seems pod are done but experiment status are not updated. Checked status using command kubectl get experiments

What did you expect to happen:
We want every individual user create experiment in their own namespace.

Environment:

  • Kubeflow version: 0.6.2
  • Kubernetes version: (use kubectl version): 1.13.8
@SatyaNarayan1
Copy link

facing the same issue kubeflow version 0.6.2. Cant see any thing in experiments UI also experiments/trials in running state.

@johnugeorge
Copy link
Member

Yes. This is a known issue. This issue will be solved in upcoming 0.7 release

@SatyaNarayan1
Copy link

@johnugeorge is there any earlier version in which experiment UI is working?

@johnugeorge
Copy link
Member

I was referring to issue where Katib job and services are in different namespaces:

Related: #343

@johnugeorge
Copy link
Member

@SatyaNarayan1 Do you have them in different namespaces?

@SatyaNarayan1
Copy link

SatyaNarayan1 commented Sep 23, 2019

@johnugeorge I tried both approach

  1. Keeping in same namespace "kubeflow"
  2. Keeping in two different namespace
    in both cases experiment UI is blank

Screen Shot 2019-09-23 at 12 25 38 PM

Screen Shot 2019-09-23 at 12 25 24 PM

@gaocegege
Copy link
Member

So, current implementation is such that we do not provide namespace, it is uses the namespace of the deployment (which is KF)

From @johnugeorge

@Jeffwan
Copy link
Member Author

Jeffwan commented Sep 26, 2019

@gaocegege @johnugeorge

New to Katib project and do we have an estimate on work to support different namespace. Since most important components are moved to multi-tenancy mode, I hope users can submit their katib experiment in their own namespace. Otherwise, user may not have permission on kubeflow in most of the enterprise envs. This should be a high priority improvement.

@gaocegege
Copy link
Member

Hi @Jeffwan
/cc @johnugeorge

I think we are going to give katib cluster scoped access and show all the experiments in all namespaces.

And I will work on it. Does it work for you?

@gaocegege
Copy link
Member

/assign

@Jeffwan
Copy link
Member Author

Jeffwan commented Sep 27, 2019

@gaocegege That makes sense. Show all experiments is good enough now.

@gaocegege
Copy link
Member

/area front-end

@gaocegege
Copy link
Member

/close

#835 #827 #839 fixed this issue.

@k8s-ci-robot
Copy link

@gaocegege: Closing this issue.

In response to this:

/close

#835 #827 #839 fixed this issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Jeffwan
Copy link
Member Author

Jeffwan commented Sep 30, 2019

Great! Thanks @gaocegege

@gaocegege
Copy link
Member

Thanks for the issue! @Jeffwan

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