OCPBUGS-18285,OCPBUGS-19479: Update to Kubernetes 1.27.6 #1709
Conversation
commit 1b3ae27e7af577372d5aaaf28ea401eb33d1c4df
Author: weizhichen <weizhichen@microsoft.com>
Date: Thu Mar 9 08:39:04 2023 +0000
fix
commit 566e139308e3cec4c9d4765eb4ccc3a735346c2e
Author: weizhichen <weizhichen@microsoft.com>
Date: Thu Mar 9 08:36:32 2023 +0000
fix unit test
commit 13a58ebd25b824dcf854a132e9ac474c8296f0bf
Author: weizhichen <weizhichen@microsoft.com>
Date: Thu Mar 2 03:32:39 2023 +0000
add unit test
commit c984e36e37c41bbef8aec46fe3fe81ab1c6a2521
Author: weizhichen <weizhichen@microsoft.com>
Date: Tue Feb 28 15:25:56 2023 +0000
fix imports
commit 58ec617e0ff1fbd209ca0af3237017679c3c0ad7
Author: weizhichen <weizhichen@microsoft.com>
Date: Tue Feb 28 15:24:21 2023 +0000
delete CheckVolumeExistenceOperation
commit 0d8cf0caa78bdf1f1f84ce011c4cc0e0de0e8707
Author: weizhichen <weizhichen@microsoft.com>
Date: Tue Feb 28 14:29:37 2023 +0000
fix 111933
… creation The topology.kubernetes.io/zone label may be added by could provider asynchronously after the Node is created. The previous code didn't update the topology cache after receiving the Node update event, causing TopologyAwareHint to not work until kube-controller-manager restarts or other Node events trigger the update. Signed-off-by: Quan Tian <qtian@vmware.com>
The member variable `cpuRatiosByZone` should be accessed with the lock acquired as it could be be updated by `SetNodes` concurrently. Signed-off-by: Quan Tian <qtian@vmware.com> Co-authored-by: Antonio Ojea <aojea@google.com>
Signed-off-by: TommyStarK <thomasmilox@gmail.com>
Signed-off-by: Etienne Champetier <e.champetier@ateme.com>
This allow for a small time jump backward after certificates generation. Signed-off-by: Etienne Champetier <e.champetier@ateme.com>
reconstructVolume() is called when kubelet may not have connection to the API server yet, therefore it cannot get CSIDriver instances to figure out if a CSI volume is attachable or not. Refactor reconstructVolume(), so it does not need FindAttachablePluginBySpec for CSI volumes, because all of them are deviceMountable (i.e. FindDeviceMountablePluginBySpec always returns the CSI volume plugin).
During CSI volume reconstruction it's not possible to tell, if the volume is attachable or not - CSIDriver instance may not be available, because kubelet may not have connection to the API server at that time. Adding uncertain state during reconstruction + adding a correct state when the API server is available.
node.status.volumesInUse should report only attachable volumes, therefore it needs to wait for the reconciler to update uncertain attachability of volumes from the API server.
To volumesNeedUpdateFromNodeStatus - because both devicePath and uncertain attach-ability needs to be fixed from node status.
to be in sync with volumesNeedUpdateFromNodeStatus.
Change-Id: Ic282a57169cab8dc498574f08b081914218a1039
# Conflicts: # pkg/controller/job/job_controller.go
ReadWriteOncePod feature needs min requirement of 1.27 kubelet, add the tag to skip test if kubelet version is smaller than 1.27 Change-Id: I27959156db90f2477cead6dfc16f42dbc54663bc
…ick-of-#118451-upstream-release-1.27 Add mininumKubelet tag into ReadWriteOncePod test
…ax seats Max seats from prioriy & fairness work estimator is now min(0.15 x nominalCL, nominalCL/handSize) 'Max seats' calculated by work estimator is currently hard coded to 10. When using lower values for --max-requests-inflight, a single LIST request taking up 10 seats could end up using all if not most seats in the priority level. This change updates the default work estimator config such that 'max seats' is at most 10% of the maximum concurrency limit for a priority level, with an upper limit of 10. This ensures seats taken from LIST request is proportional to the total available seats. Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
image_list.go is one of the files included in the non-test variant Go build list, but its getSampleDevicePluginPod function references readDaemonSetV1OrDie function defined in device_plugin_test.go which is included in the test variant Go build list only. (The file name is *_test.go). As a result, "go build" fails with the undefined reference error. In practice, that may not be an issue since k8s project contributors aren't meant to run go build on this package. However, tools that depend on go build to operate - e.g., gopls or govulncheck ./... - will report this as an error. Fix this error and make test/e2e package pass go build by moving this file to also test-only source code.
…y-pick-of-#118601-origin-release-1.27 Automated cherry pick of kubernetes#118601: priority & fairness: support dynamic max seats
…f-#118549-upstream-release-1.27 Automated cherry pick of kubernetes#118549: fix 'pod' in kubelet prober metrics
…ick-of-#118922-upstream-release-1.27 Automated cherry pick of kubernetes#118922: kubeadm: backdate generated CAs
…k-of-#119434-upstream-release-1.27 Automated cherry pick of kubernetes#119434: Include ignored pods when computing backoff delay for Job pod
…of-#116134-origin-release-1.27 Automated cherry pick of kubernetes#116134: fix: After a Node is down and take some time to get back to up again, the mount point of the evicted Pods cannot be cleaned up successfully.
…-pick-of-#117449-upstream-release-1.27 Automated cherry pick of kubernetes#117449: e2e: fix flaky test 'should contain OpenAPI V3 for Aggregated
…ck-of-#117710-upstream-release-1.27 Automated cherry pick of kubernetes#117710: e2e_node: move getSampleDevicePluginPod to
…ick-of-#117804-upstream-release-1.27 Automated cherry pick of kubernetes#117804: Refactor FindAttachablePluginBySpec out of CSI code path
…of-#117245-kubernetes#117249-upstream-release-1.27 Automated cherry pick of kubernetes#117245: Fix TopologyAwareHint not working when zone label is added kubernetes#117249: Fix a data race in TopologyCache
sdodson
added
the
jira/valid-bug
openshift-ci
bot
added
backports/validated-commits
|
/override ci/prow/verify-commits |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bertinatto, soltysh 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 |
openshift-ci
bot
added
the
approved
|
@soltysh: Overrode contexts on behalf of soltysh: 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. |
|
/label backport-risk-assessed |
openshift-ci
bot
added
the
backport-risk-assessed
openshift-ci
bot
assigned duanwei33, gangwgr, kasturinarra, sunilcio, wangke19, xingxingxia and zhouying7780
|
/label cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
/test e2e-azure-ovn-upgrade |
1 similar comment
|
/test e2e-azure-ovn-upgrade |
|
The 504 Gateway issue is a known problem tracked in https://issues.redhat.com/browse/OCPBUGS-18999 and we also got a green azure-ovn-upgrade in https://pr-payload-tests.ci.openshift.org/runs/ci/2fa51ea0-5798-11ee-8dd2-90e5dbb2a705-1 so I'm confident this is not broken. |
|
@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-azure-ovn-upgrade 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. |
|
@bertinatto: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
openshift-merge-robot
merged commit 1648878
into
openshift:release-4.14
|
@bertinatto: Jira Issue OCPBUGS-18285: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-18285 has been moved to the MODIFIED state. Jira Issue OCPBUGS-19479: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-19479 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. |
|
Fix included in accepted release 4.14.0-0.nightly-2023-09-22-154021 |
/assign @soltysh