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.

Sign up for GitHub

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

Jump to bottom

OAth client instructions are ambiguous #586

Closed
vfontama opened this issue Dec 21, 2018 · 8 comments
Closed

OAth client instructions are ambiguous #586

vfontama opened this issue Dec 21, 2018 · 8 comments
Assignees
@sarahmaddox

Comments

@vfontama
Copy link

The instructions to create credentials is a bit ambiguous. Specifically, in step 2 where we set the "Authorized redirect URIs" the instructions have this sample: "https://.endpoints..cloud.goog/_gcp_gatekeeper/authenticate".

The is straightforward. However, the is confusing. It is not clear which name to use: In the screenshot the "Name" field has a different name from the name used in the "Authorized redirect URIs" field. So it's not clear if we should use the same name or not.

screen shot 2018-12-21 at 12 21 45 pm
@yebrahim
Copy link
Contributor

/assign @jlewi
/assign @kunmingg
I thought this can be clearer as well, any thoughts guys?

@kunmingg
Copy link

docs located at: https://github.com/kubeflow/website/blob/master/content/docs/started/getting-started-gke.md

@sarahmaddox
Copy link
Contributor

+1 that it's confusing. The "Name" in the UI is an arbitrary name that the user gives to this particular OAuth client ID. I'll clarify that in the docs.

/assign

@sarahmaddox
Copy link
Contributor

/unassign @jlewi jlewi
/unassign @kunmingg

@sarahmaddox sarahmaddox mentioned this issue Dec 22, 2018
Closed
@sarahmaddox
Copy link
Contributor

This issue was moved to kubeflow/website#376

@sarahmaddox
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@sarahmaddox: Closing this issue.

In response to this:

/close

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.

1 similar comment
@k8s-ci-robot
Copy link
Contributor

@sarahmaddox: Closing this issue.

In response to this:

/close

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.

Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
@jlewi @k8s-ci-robot
Only keep the 3 most recent auto deployments for each version. (kubef…
8bc32fd 
…low#586)

* For each KF version (master, v1.0, etc...) we only want to keep
  the most recent N deployments (N=3 right now). Otherwise we end up
  running out of quota in the deployments project.

* Fix kubeflow/testing#584 out of quota errors due too many auto deployed
  clusters
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
@yhwang
[test] Add trusted-ai into e2e testing (kubeflow#586)
4ae035e 
Add trusted-ai into the e2e testing and a flag (extra-test-cases)
to enable it. Also refactor the e2e-test task to support more test cases.

Signed-off-by: Yihong Wang <yh.wang@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sarahmaddox sarahmaddox

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jlewi @yebrahim @sarahmaddox @k8s-ci-robot @vfontama @kunmingg