-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite} #27328
Comments
Failed: Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite}
|
@pwittrock which PR were you referring to? |
Both happened at |
Failed: Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite}
|
Failed: Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite}
|
Failed: Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite}
|
Automatic merge from submit-queue Retry Pod/RC updates in kubectl rolling-update Fixes #27328 @kubernetes/kubectl [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/4156/
Failed: Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite}
The text was updated successfully, but these errors were encountered: