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

Move kubebench package to kubeflow repo #1513

Closed

xyhuang opened this issue Sep 11, 2018 · 1 comment

Assignees

Member

xyhuang commented Sep 11, 2018

Currently the ks package of kubebench project resides in kubebench repo. This proposes moving it to kubeflow repo.

Member Author

xyhuang commented Sep 11, 2018

/assign

k8s-ci-robot assigned xyhuang

xyhuang mentioned this issue

Add Kubebench package #1531

Merged

k8s-ci-robot closed this as completed in #1531

surajkota pushed a commit to surajkota/kubeflow that referenced this issue


          Remove http from the GCP ingress and explicitly set the default backe…

3306cdc

…nd. (kubeflow#1513)

* Ref https://cloud.google.com/kubernetes-engine/docs/concepts/ingress-xlb#disabling_http force all traffic from client to ingress to be https.

* Fix GoogleCloudPlatform/kubeflow-distribution#116

* Explicitly set the default backend for the GCP ingress.

  * https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#default_backend

  * This prevents a separate forwarding rule from being created which is
    confusing.

aliceUnhinged613 mentioned this issue

[Snyk] Security upgrade node-fetch from 2.6.0 to 3.2.10 aliceUnhinged613/kubeflow#110

Open

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