Skip to content

Conversation

bertinatto
Copy link
Member

No description provided.

k8s-ci-robot and others added 30 commits July 28, 2025 23:18
Adding check for nil pod resources in huge pages test
…flake

Fix apiserver service proxying e2e test flakiness
…expected network errors

Signed-off-by: Anish Ramasekar <[email protected]>
feat: trigger PreBindPreFlight in the binding cycle
…cycle

Fix prerelease-lifecycle for volumeattributesclass
…ding-conditions

Implement DRA Device Binding Conditions (KEP-5007)
* HPA support for pod-level resource specifications

* Add e2e tests for HPA support for pod-level resource specifications
Clear pod.Status.NominatedNodeName when pod is bound
…ation

Fix incorrect validation on the kubelet
…ssue_133249

test: fix TestStructuredAuthenticationConfigReload flake by handling expected network errors
When pod-level resources are detected, the cpu and memory manages
cannot engage because the feature is not yet compatible,
one of the main reasons being the managers only work at container level.

So, the managers has to detect if pod level resources are in use,
and turn themselves to no-operation skipping resource allocation
should that be the case.

We add an intentional loud log to inform the user, because
pods with pod-level resources landing on a node which cannot
actuate the desired spec is likely to be undesirable.

Signed-off-by: Francesco Romani <[email protected]>
Signed-off-by: Francesco Romani <[email protected]>
…nslator_WebSocketServerErrors

Deflake test stream translator web socket server errors
Add / update kubelet and DRA API owners
…_all_cases

KEP-5278 Stop clearing NominatedNodeName in all cases
Miciah and others added 18 commits October 6, 2025 13:43
This commit fixes bug 1919737.

https://bugzilla.redhat.com/show_bug.cgi?id=1919737

* pkg/proxy/iptables/proxier.go (syncProxyRules): Prefer a local endpoint
for the cluster DNS service.
Explicitly exclude etcd and etcd-readiness checks (OCPBUGS-48177)
and have etcd operator take responsibility for properly reporting etcd readiness.
Justification: kube-apiserver instances get removed from a load balancer when etcd starts
to report not ready (as will KA's /readyz). Client connections can withstand etcd unreadiness
longer than the readiness timeout is. Thus, it is not necessary to drop connections
in case etcd resumes its readiness before a client connection times out naturally.
This is a downstream patch only as OpenShift's way of using etcd is unique.
Signed-off-by: Peter Hunt <[email protected]>

UPSTREAM: <carry>: authorization: add minimumkubeletversion package

MinimumKubeletVersion is a way for an admin to declare that nodes any older than the
minimum version cannot authorize with the apiserver. This effectively prevents them from joining.

Doing so means the apiservers can trust newer features are usable on clusters with version skews

Signed-off-by: Peter Hunt <[email protected]>

UPSTREAM: <carry>: authorizer: move mininum kubelet version authorizer to pkg/kubeapiserver and add authorization mode

this does require a line of code be moved from the enablement package to stop a cyclical import

Signed-off-by: Peter Hunt <[email protected]>

UPSTREAM: <carry>: crdvalidation: move latency profile file to be agnostic of field

Signed-off-by: Peter Hunt <[email protected]>

UPSTREAM: <carry>: features: add MinimumKubeletVersion feature

Signed-off-by: Peter Hunt <[email protected]>
Upstream enables volume group snapshots by editing yaml files in a shell
script [1]. We can't use this script in openshift-tests.

Create a brand new, OCP specific test driver based on csi-driver-hostpath,
only with the --feature-gate=VolumeGroupSnapshot on external-snapshotter command line.

We will need to carry this patch until the feature graduates to GA. I've
chosen to create brand new files in this carry patch, so it can't conflict
with the existing ones.

1: https://github.com/kubernetes/kubernetes/blob/91d6fd3455c4a071408df20c7f48df221f2b6d30/test/e2e/testing-manifests/storage-csi/external-snapshotter/volume-group-snapshots/run_group_snapshot_e2e.sh
Add featuregate for performantsecuritypolicy for storage
This should avoid races between pvc creation and quota creation
…TClient.

Authorization, token authentication, imagepolicy admission, and audit webhooks configure RESTClients
that encode to JSON regardless of the ContentType of the provided rest.Config. Because this is
opaque to the RESTClient, configuring a ContentType other than "application/json" results in
requests with JSON-encoded bodies and a non-JSON media type in the Content-Type header. Webhook
servers that respect the Content-Type request header will be unable to decode an object from the
request body.

Explicitly overriding the ContentType of the provided rest.Config fixes this issue and is consistent
with how clients are constructed for conversion and admission webhooks.
…version.

Backported from 799312a upstream - drop once we rebase onto a version that has it.
…ver manifest

Update image from v1.7.3 to v1.16.1 to avoid pulling multiple
in CI.
… expired credential, remove credential, add TODOs"

This reverts commit a2ef871.

That commit removed a test that we already skip in OCP. The patch also removed
an image from an iota-based enum, which caused images returned by the
`openshift-tests tests images` command to be renamed. Ultimately, this broke
metal jobs because the list of images returned by `openshift-tests` was not
the same as the list required by the tests.

This change provides a temporary fix until a proper solution is implemented.
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link

openshift-ci bot commented Oct 6, 2025

@bertinatto: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-crun-wasm f194ef5 link true /test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-cgroupsv2 f194ef5 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-fips f194ef5 link true /test e2e-aws-ovn-fips
ci/prow/okd-scos-e2e-aws-ovn f194ef5 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-hypershift f194ef5 link true /test e2e-aws-ovn-hypershift

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-sigs/prow repository. I understand the commands that are listed here.

@bertinatto
Copy link
Member Author

/payload 4.21 nightly blocking
/payload 4.21 nightly informing

Copy link

openshift-ci bot commented Oct 7, 2025

@bertinatto: trigger 13 job(s) of type blocking for the nightly release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-1of2
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-2of2
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-1of3
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-3of3
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5f5792d0-a319-11f0-9d0d-0e5625475ae0-0

trigger 67 job(s) of type informing for the nightly release of OCP 4.21

  • periodic-ci-openshift-release-master-nightly-4.21-e2e-agent-compact-fips
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-agent-ha-dualstack-conformance
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-agent-single-node-ipv6-conformance
  • periodic-ci-openshift-release-master-nightly-4.21-console-aws
  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-periodics-e2e-aws
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-csi
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-cgroupsv2
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-fips
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-single-node-csi
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-single-node-techpreview
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-single-node-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.21-upgrade-from-stable-4.20-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-upgrade-out-of-change
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upi
  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-periodics-e2e-azure
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-azure-csi
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade-out-of-change
  • periodic-ci-openshift-release-master-cnv-nightly-4.21-deploy-azure-kubevirt-ovn
  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-periodics-e2e-gcp
  • periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-gcp-ovn-csi
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-gcp-ovn-rt
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-gcp-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-azure-kubevirt-ovn
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-dualstack
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-dualstack-techpreview
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-ipv6-techpreview
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-serial-virtualmedia-1of2
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-serial-virtualmedia-2of2
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-techpreview
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.21-upgrade-from-stable-4.20-e2e-metal-ipi-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-serial-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-serial-ovn-dualstack
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-upgrade-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.21-upgrade-from-stable-4.20-e2e-metal-ipi-upgrade-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.21-metal-ovn-single-node-recert-cluster-rename
  • periodic-ci-openshift-osde2e-main-nightly-4.21-osd-aws
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-osd-ccs-gcp
  • periodic-ci-openshift-osde2e-main-nightly-4.21-osd-gcp
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-proxy
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ovn-single-node-live-iso
  • periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.21-nightly-x86-payload-control-plane-6nodes
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-telco5g
  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-csi
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-serial
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-techpreview
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.21-e2e-vsphere-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-vsphere-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-upi
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-upi-serial
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-static-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5f5792d0-a319-11f0-9d0d-0e5625475ae0-1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.