-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
E2E test verifies Kubeflow installed via Deployment Manager #836
Labels
Comments
I think we should do the following
|
jlewi
added a commit
to jlewi/kubeflow
that referenced
this issue
May 24, 2018
* The script replaces our bash script. * A python script should make it easier to make our tests more robust by adding retries and error handling. Related to kubeflow#836 verify Kubeflow deployed correctly with deployment manager.
jlewi
added a commit
to jlewi/kubeflow
that referenced
this issue
May 24, 2018
* The script replaces our bash script. * A python script should make it easier to make our tests more robust by adding retries and error handling. Related to kubeflow#836 verify Kubeflow deployed correctly with deployment manager.
jlewi
added a commit
to jlewi/kubeflow
that referenced
this issue
May 24, 2018
…nager. * The scripts replaces our bash commands * For teardown we want to add retries to better handle INTERNAL_ERRORS with deployment manager that are causing the test to be flaky. Related to kubeflow#836 verify Kubeflow deployed correctly with deployment manager.
jlewi
added a commit
to jlewi/kubeflow
that referenced
this issue
May 24, 2018
…nager. * The scripts replaces our bash commands * For teardown we want to add retries to better handle INTERNAL_ERRORS with deployment manager that are causing the test to be flaky. Related to kubeflow#836 verify Kubeflow deployed correctly with deployment manager. * Fix resource_not_found errors in delete (kubeflow#833) * The not found error was due to the type providers for K8s resources being deleted before the corresponding K8s resources. So the subsequent delete of the K8s resource would fail because the type provider did not exist. * We fix this by using a $ref to refer to the type provider in the type field of K8s resources.
k8s-ci-robot
pushed a commit
that referenced
this issue
May 25, 2018
…er. (#866) * Create python scripts for deploying Kubeflow on GCP via deployment manager. * The scripts replaces our bash commands * For teardown we want to add retries to better handle INTERNAL_ERRORS with deployment manager that are causing the test to be flaky. Related to #836 verify Kubeflow deployed correctly with deployment manager. * Fix resource_not_found errors in delete (#833) * The not found error was due to the type providers for K8s resources being deleted before the corresponding K8s resources. So the subsequent delete of the K8s resource would fail because the type provider did not exist. * We fix this by using a $ref to refer to the type provider in the type field of K8s resources. * * deletePolicy can't be set per resource * Autoformat jsonnet.
saffaalvi
pushed a commit
to StatCan/kubeflow
that referenced
this issue
Feb 11, 2021
…er. (kubeflow#866) * Create python scripts for deploying Kubeflow on GCP via deployment manager. * The scripts replaces our bash commands * For teardown we want to add retries to better handle INTERNAL_ERRORS with deployment manager that are causing the test to be flaky. Related to kubeflow#836 verify Kubeflow deployed correctly with deployment manager. * Fix resource_not_found errors in delete (kubeflow#833) * The not found error was due to the type providers for K8s resources being deleted before the corresponding K8s resources. So the subsequent delete of the K8s resource would fail because the type provider did not exist. * We fix this by using a $ref to refer to the type provider in the type field of K8s resources. * * deletePolicy can't be set per resource * Autoformat jsonnet.
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Feb 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background:
#823 Start Deploying bootstrapper via deployment manager
#757 Install Kubeflow by the deployment manager
To verify this is working we need to update the E2E test to verify that Kubeflow is actually deployed correctly. I think this is currently blocked by #832
/assign @kunmingg
The text was updated successfully, but these errors were encountered: