Bug 1873043: Rebase 1.19.0 #325
Conversation
test/e2e: fail test rather than flooding logs if PVC watch is closed prematurely
…ormer Fix /readyz to contain informer-sync
Mark cloud provider InstanceV2 as experimental and remove provider ID references
Update Cluster Autoscaler version to 1.19.0
Signed-off-by: knight42 <anonymousknight96@gmail.com>
fix: deflake run_kubectl_apply_tests
- ensure endpoints that have been deleted and are desired are recreated despite a possibly out of date endpoint cache
…ing-tracker-fix Fixing memory leak in EndpointSliceMirroring EndpointSlice tracker
Deflake TestExpectationsOnRecreate
Deflake TestUpdateNodeStatusWithLease - guard cached machineInfo
Add missing ppc64le architecture in the get-kube* scripts
e2e delete namespaces after finish
Make AttachDisk for EBS idempotent again
…Score plugins The lack of this validation on incoming pods causes unpredictable cluster outcomes when later calculating affinity results against existing pods (see kubernetes#92714). This fix quickly addresses the main source where these problems should be caught. It is unfortunately difficult to add this validation directly to the API server due to the fact that it may break migrations with existing pods that fail this check. This is a compromise to address the current issue.
Add the check for test cluster when starting csi proxy
[go1.15] Use errors.As to unwrap net errors
Deflake LimitRange e2e test
Add LabelSelector validation in Pod Affinity/AntiAffinity Filter and Score plugins
marun
force-pushed
the
rebase-1.19.0
branch
from
c8a4e3c
to
cbb9060
Compare
|
Picked #338 since its merge forced a retest and stripped the override for verify-commits. |
openshift-ci-robot
added
the
do-not-merge/invalid-owners-file
|
/retest |
marun
force-pushed
the
rebase-1.19.0
branch
from
cbb9060
to
972d51f
Compare
|
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
|
/retest |
|
/override ci/prow/verify-commits |
sttts
removed
the
do-not-merge/invalid-owners-file
|
/override ci/prow/verify-commits |
|
@sttts: Overrode contexts on behalf of sttts: ci/prow/e2e-cmd, ci/prow/verify-commits In response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: marun, sttts 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 |
|
@sttts: Overrode contexts on behalf of sttts: ci/prow/verify-commits In response to this:
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. |
|
@marun: All pull requests linked via external trackers have merged:
Bugzilla bug 1873043 has been moved to the MODIFIED state. In response to this:
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. |
verify-commitsjob will need to be overridden to merge due to the presence of un-prefixed commits in the base kube branch.do-not-merge/invalid-owners-filelabel, which is applied due to the presence of upstream kube contributors in OWNERS files that do not belong to the openshift org.