-
Notifications
You must be signed in to change notification settings - Fork 11
Aggregate failed workload conditions into CR #23
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
Conversation
Signed-off-by: Alex Kalenyuk <[email protected]>
e9ccdd6 to
519ef97
Compare
519ef97 to
e689fd4
Compare
|
/retest |
e689fd4 to
b0d89ad
Compare
|
/test all |
|
@akalenyu: The following test failed, say
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. I understand the commands that are listed here. |
|
/test all |
1 similar comment
|
/test all |
ded2113 to
3b5e705
Compare
Broke after we bumped and got kubernetes-sigs/controller-runtime#1399 Signed-off-by: Alex Kalenyuk <[email protected]>
Signed-off-by: Alex Kalenyuk <[email protected]>
3b5e705 to
407ea84
Compare
|
/cc @mhenriks @tiraboschi |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: akalenyu, mhenriks, tiraboschi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Currently, we just dangle in
Deployingphase when things go badly, althoughthe deployment conditions API provides more information such as
Progressing=falsethat we can use to better capture the status of install.