-
Notifications
You must be signed in to change notification settings - Fork 125
[WIP] enable DRA by default in 4.20 #2471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-4.20
Are you sure you want to change the base?
Conversation
DRA e2e tests use the `hostpathplugin:v1.7.3` image https://github.com/kubernetes/kubernetes/blob/1b4c5b3f8605dc1c86050ae941a24556d4fbd678/test/e2e/testing-manifests/dra/dra-test-driver-proxy.yaml#L50 today the `appendCSIImageConfigs` function gathers CSI images from the `storage-csi` folder only, and the DRA tests use a separate version of the `hostpathplugin` than what is gathered from the `storage-csi` folder. As a consequence the generated image list does not include the version of the `hostpathplugin` image used by the DRA tests. This PR adds the `dra` folder to the CSI image gathering function. The output of the test: ``` go test -v -count=1 ./test/utils/image -run=TestCSIImageConfigs === RUN TestCSIImageConfigs csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: csi-external-health-monitor-controller, version: v0.12.1 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: csi-attacher, version: v4.8.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: csi-provisioner, version: v5.1.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: csi-resizer, version: v1.13.1 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: csi-snapshotter, version: v8.2.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/cloud-provider-gcp, name: gcp-compute-persistent-disk-csi-driver, version: v1.4.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: volume-data-source-validator, version: v1.0.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: hostpathplugin, version: v1.16.1 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: csi-node-driver-registrar, version: v2.13.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: livenessprobe, version: v2.15.0 csi_manifests_test.go:59: found image: registry: registry.k8s.io/e2e-test-images, name: busybox, version: 1.36.1-1 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: hostpathplugin, version: v1.7.3 csi_manifests_test.go:59: found image: registry: registry.k8s.io/sig-storage, name: hello-populator, version: v1.0.1 --- PASS: TestCSIImageConfigs (0.01s) ```
this is an experiment, once we prove that it works when dra e2e tests pass and the openshift/api pr merges then we drop it
@tkashem: 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 |
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn openshift/api#2483 |
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn openshift/api#2483 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tkashem 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 |
|
||
DynamicResourceAllocation: { | ||
{Version: version.MustParse("1.26"), Default: false, PreRelease: featuregate.Alpha}, | ||
{Version: version.MustParse("1.32"), Default: false, PreRelease: featuregate.Beta}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we didn't need this piece if we have the o/api pieces, because the cluster config operator will configure the feature gates enabled in the default set
if err != nil { | ||
panic(err) | ||
for _, dir := range []string{"storage-csi", "dra"} { | ||
err := fs.WalkDir(embeddedFS, dir, walkDirFn) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not using walkDirFn ?
networkingapiv1beta1.SchemeGroupVersion, | ||
resourcev1beta1.SchemeGroupVersion, | ||
resourcev1beta2.SchemeGroupVersion, | ||
// we enable DRA v1beta1 and v1beta2 APIs to achieve AI comformance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: conformance*
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn openshift/api#2483 |
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/470510a0-94ae-11f0-9af7-661a632cc2e9-0 |
/retest |
today kas operator enables the resource v1beta1 and v1beta2 apis if it sees the DynamicResourceAllocation feature gate. but it seems, if we are to enable the apis and the feature then enabling it here seems safer
@tkashem: 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 |
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn openshift/api#2483 openshift/origin#30283 |
@tkashem: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6e596100-957c-11f0-8018-e8d3abd6f90e-0 |
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn openshift/api#2483 openshift/origin#30283 |
@tkashem: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b7f40a80-957d-11f0-8cc1-ed039260cff2-0 |
@tkashem: 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 |
/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn openshift/api#2483 openshift/origin#30283 |
@tkashem: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fbab7f90-959d-11f0-8641-441a18ef305d-0 |
@tkashem: 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-sigs/prow repository. I understand the commands that are listed here. |
No description provided.