Skip to content

Conversation

@sairameshv
Copy link
Member

@sairameshv sairameshv commented Oct 1, 2025

  • DRA has been graduated to GA in pstream from K8s-1.34
  • DynamicResourceAllocation featuregate is enabled for TPNU cluster types in Openshift
  • Hence, the tests need to be enabled to get some signal so that the featuregate can be enabled for the Default cluster types as well
  • Also, disabled the tests that run based out of DRA's beta API as we don't enable the beta APIs downstream and only depend on the GA'ed APIs

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Enables the DRA related tests to be run for all the techpreview jobs

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

This is to get some signal from sippy so that the featuregate can be removed/enable for the all/default cluster types

Does this PR introduce a user-facing change?

"NONE"

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Oct 1, 2025
@openshift-ci openshift-ci bot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Oct 1, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 1, 2025
@openshift-ci-robot
Copy link

@sairameshv: This pull request references Jira Issue OCPBUGS-61381, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lyman9966

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

  • DRA has been graduated to GA in pstream from K8s-1.34
  • DynamicResourceAllocation featuregate is enabled for TPNU cluster types in Openshift
  • Hence, the tests need to be enabled to get some signal so that the featuregate can be enabled for the Default cluster types as well

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Enables the DRA related tests to be run for all the techpreview jobs

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

This is to get some signal from sippy so that the featuregate can be removed/enable for the all/default cluster types

Does this PR introduce a user-facing change?

"NONE"

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

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

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
Copy link

openshift-ci bot commented Oct 1, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sairameshv
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sairameshv
Copy link
Member Author

I would like to monitor the TP enabled jobs i.e. ci/prow/e2e-aws-ovn-techpreview, ci/prow/e2e-aws-ovn-techpreview-serial to look out for the DRA related e2e tests

@openshift-ci-robot
Copy link

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

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

@sairameshv: This pull request references Jira Issue OCPBUGS-61381, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lyman9966

In response to this:

  • DRA has been graduated to GA in pstream from K8s-1.34
  • DynamicResourceAllocation featuregate is enabled for TPNU cluster types in Openshift
  • Hence, the tests need to be enabled to get some signal so that the featuregate can be enabled for the Default cluster types as well
  • Also, disabled the tests that run based out of DRA's beta API as we don't enable the beta APIs downstream and only depend on the GA'ed APIs

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Enables the DRA related tests to be run for all the techpreview jobs

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

This is to get some signal from sippy so that the featuregate can be removed/enable for the all/default cluster types

Does this PR introduce a user-facing change?

"NONE"

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

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

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.

@sairameshv
Copy link
Member Author

/cc @tkashem

@openshift-ci openshift-ci bot requested a review from tkashem October 8, 2025 13:32
…gate

- Fixes OCPBUGS-61381, enables DRA related tests from OCP-4.21
- DRA has been graduated to GA in upstream from K8s-1.34 i.e OCP-4.21
- These tests need to be enabled to get some signal so that the featuregate can be enabled for the Default cluster types in o/api
- Disabling the tests that run on the DRA beta APIs as we support the GA
  APIs only

Signed-off-by: Sai Ramesh Vanka <[email protected]>
@openshift-ci-robot
Copy link

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

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.

"[sig-node] ImageCredentialProvider [Feature:KubeletCredentialProviders] should be able to create pod with image credentials fetched from external credential provider",
},
// tests for beta APIs that are not enabled
"DisabledResourceBetaAPI": {
Copy link
Member Author

@sairameshv sairameshv Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @jacobsee , @bertinatto
I know you have been working on the rebase and so the disabling of DRA beta related tests from your commit of the 1.34 rebase PR

Do you think this change of keeping the beta tests under a separate key "DisabledResourceBetaAPI" makes sense? If so, do you want to pick this commit as part of the rebase PR?

@openshift-ci
Copy link

openshift-ci bot commented Oct 8, 2025

@sairameshv: 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-csi 5385fe7 link false /test e2e-aws-csi
ci/prow/e2e-aws-ovn-techpreview-serial 5385fe7 link false /test e2e-aws-ovn-techpreview-serial
ci/prow/e2e-aws-ovn-techpreview 5385fe7 link false /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-crun-wasm c348e5d link true /test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-fips c348e5d link true /test e2e-aws-ovn-fips
ci/prow/e2e-metal-ipi-ovn-ipv6 c348e5d link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-runc c348e5d link true /test e2e-aws-ovn-runc
ci/prow/e2e-gcp c348e5d link true /test e2e-gcp
ci/prow/k8s-e2e-conformance-aws c348e5d link true /test k8s-e2e-conformance-aws
ci/prow/okd-scos-e2e-aws-ovn c348e5d link false /test okd-scos-e2e-aws-ovn
ci/prow/k8s-e2e-gcp-ovn c348e5d link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-aws-ovn-crun c348e5d link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-cgroupsv2 c348e5d link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-serial c348e5d link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-hypershift c348e5d 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.

@sairameshv
Copy link
Member Author

Closing the PR as this is already addressed as part of the 1.34 rebase PR's commit

@sairameshv sairameshv closed this Oct 9, 2025
@openshift-ci-robot
Copy link

@sairameshv: This pull request references Jira Issue OCPBUGS-61381. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

  • DRA has been graduated to GA in pstream from K8s-1.34
  • DynamicResourceAllocation featuregate is enabled for TPNU cluster types in Openshift
  • Hence, the tests need to be enabled to get some signal so that the featuregate can be enabled for the Default cluster types as well
  • Also, disabled the tests that run based out of DRA's beta API as we don't enable the beta APIs downstream and only depend on the GA'ed APIs

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Enables the DRA related tests to be run for all the techpreview jobs

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

This is to get some signal from sippy so that the featuregate can be removed/enable for the all/default cluster types

Does this PR introduce a user-facing change?

"NONE"

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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 openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants