-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(docs): updated readme wait condition #5371
fix(docs): updated readme wait condition #5371
Conversation
/assign @Bobgy |
@@ -30,7 +30,7 @@ It's based on in-cluster PersistentVolumeClaim storage. | |||
kubectl apply -k cluster-scoped-resources/ | |||
kubectl wait crd/applications.app.k8s.io --for condition=established --timeout=60s | |||
kubectl apply -k env/platform-agnostic/ | |||
kubectl wait applications/pipeline -n kubeflow --for condition=Ready --timeout=1800s | |||
kubectl wait pods -l application-crd-id=kubeflow-pipelines -n kubeflow --for condition=Ready --timeout=1800s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for flagging this problem!
I think the change is reasonable for backward compatibility.
But we may need a better label selector, because the current one is related to application again.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy 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 |
/lgtm |
Description of your changes:
For kubeflow version 1.4 the
env/platform-agnostic
dont rely on kubernetesapplications
so suggest that we look at the pods instead for the wait condition.Checklist:
Do you want this pull request (PR) cherry-picked into the current release branch?
Learn more about cherry-picking updates into the release branch.