Cherrypick to 0.5 #2849
Cherrypick to 0.5 #2849
Conversation
…2795) * Extend the E2E test for the go binary to verify that Kubeflow is deployed. * Related to kubeflow#2610 E2E test for go binary. * Create kf_is_ready_test.py to verify that Kubeflow is deployed successfully. * We don't reuse wait_for_kubeflow.py because that is configured to wait on JupyterHub. * We could have modified wait_for_kubeflow.py but I took this as an opportunity to convert the test to use pytest. * We don't run the component tests because those are currently configured to depend on wait_for_kubeflow.py. So we will modify them in a follow on PR. * kfctl_delete is now passing so enable it. * Address comments. * Disable katib stduy job test because it is flaky (Related to kubeflow#2825).
* update some image for 0.5 * update tfjob
…atform is not gcp' (kubeflow#2827)
* AddNamedContext * temp * add namespace * optionally write to KUBECONFIG * updates * revert * add verify_kubeconfig * log * add strip * fix * call AddNamedContext in Apply
* update * fix
…127.0.0.1' (kubeflow#2813) * fixes 'kfctl apply fails to create k8s resources; tries to deploy to 127.0.0.1' * remove run_with_retries for kfctl_go_test kfctl apply use case
* Add an E2E test for kfctl with IAP on GCP. Related to: kubeflow#2610 E2E test for kfctl. * Make test names unique based on parameters. * Revert to pulling HEAD. * Fix comment. * Set requests & limits. * Increase timeout. * Add a comment.
* use YAML support for IAM bindings * write to iam_bindings.yaml * yaml config to cluster-kubeflow * yaml support to storage-kubeflow * comments * fix * add desc
…ubeflow#2810) * call package manager, then platform in delete. Allow ksonnet to delete k8s * fix logic around deletion of ALL and PLATFORM * compilation error * convert to KfError on error returns * update on code comments, make sure all errors are returned as KfError
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the ℹ️ Googlers: Go here for more info. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
Cherrypick all PRs from 03/26 to now into 0.5
(PR2787 on 03/26 already cherrypicked before.)
See master commits:
https://github.com/kubeflow/kubeflow/commits/master
And 0.5 commits:
https://github.com/kubeflow/kubeflow/commits/v0.5-branch
/cc @jlewi
This change is