[WIP] Update to tip of kubernetes/kubernetes #1614
Conversation
openshift-ci-robot
added
the
backports/unvalidated-commits
|
/test unit |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
/test unit |
|
/test e2e-gcp |
|
Pushed a new update, so retest: /test verify |
|
/test unit |
|
/test verify |
|
/test unit |
|
/test e2e-aws-ovn-serial |
openshift-merge-robot
added
the
needs-rebase
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bertinatto 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 |
openshift-merge-robot
removed
the
needs-rebase
|
/test unit |
|
/test unit |
We need this in order to be able to retrieve better reports from PodSecurityViolation alerts. UPSTREAM: <carry>: PSa metrics: unset ocp_namespace on non-platform namespaces
…aged is enabled Previously, cpu load balancing was enabled in cri-o by manually changing the sched_domain of cpus in sysfs. However, RHEL 9 dropped support for this knob, instead requiring it be changed in cgroups directly. To enable cpu load balancing on cgroupv1, the specified cgroup must have cpuset.sched_load_balance set to 0, as well as all of that cgroup's parents, plus all of the cgroups that contain a subset of the cpus that load balancing is disabled for. By default, all cpusets inherit the set from their parent and sched_load_balance as 1. Since we need to keep the cpus that need load balancing disabled in the root cgroup, all slices will inherit the full cpuset. Rather than rebalancing every cgroup whenever a new guaranteed cpuset cgroup is created, the approach this PR takes is to set load balancing to disabled for all slices. Since slices definitionally don't have any processes in them, setting load balancing won't affect the actual scheduling decisions of the kernel. All it will do is open the opportunity for CRI-O to set the actually set load balancing to disabled for containers that request it. Signed-off-by: Peter Hunt <pehunt@redhat.com>
UPSTREAM: <carry>: Change annotation mechanics to allow injecting testMaps and filter out tests UPSTREAM: <carry>: Move k8s-specific rules to our fork UPSTREAM: <carry>: Create minimal wrapper needed to run k8s e2e tests
If it is useful we will combine this with the following carry: 20caad9: UPSTREAM: 115328: annotate early and late requests
…util/managedfields Some of the code we use in openshift-tests was recently made internal in kubernetes#115065. This patch exposes the code we need there.
…rs from lb when unready workaround to mitigate issue: kubernetes-sigs/cloud-provider-azure#3500 bug: https://issues.redhat.com/browse/OCPBUGS-7359 UPSTREAM: <carry>: legacy-cloud-providers: azure: use kube-proxy based health probes by default See issue: kubernetes-sigs/cloud-provider-azure#3499 bug: https://issues.redhat.com/browse/OCPBUGS-7359
…hen using static cpu manager policy There are situations where cpu load balance disabling is desired when the kubelet is not in managed state. Instead of using that condition, set the cpu load balancing parameter for new slices when the cpu policy is static Signed-off-by: Peter Hunt <pehunt@redhat.com>
…rnetes.default.svc, don't wait for aggregated availability
They are not working properly in upstream.
…nsitionTime and SidecarContainers alpha features
These were brought back in o/o PRs as follows: - netpol - openshift/origin#26775 - schedulerpreemption - openshift/origin#27874
…mespacesStatelessPodsSupport See commit 531d38e.
…cted permissions watch-termination uses lumberjack for loging. it creates permissive files by default 0644 and at the moment there is no way to specify permission while creating a file, the only way to workaround is to create a file before. this pr touches a file with restrictive permissions 0600 and relies on the fact that lumberjack respects and copies permission over if the file already exist
|
/test verify |
|
@bertinatto: The following tests 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. |
Auto-generated by https://github.com/bertinatto/ocp-next.