WIP Test driver config #403
Conversation
Signed-off-by: Grant Griffiths <[email protected]>
Add snapshotter CRDs after cluster setup
Adding build for ppc64le
kind v0.6.0 appends the kubeconfig with the default config at ~/.kube/config.
Use kind v0.6.0
…ure can be tested. Test cases that test accessing volumes from multiple nodes need to be skipped
Signed-off-by: Grant Griffiths <[email protected]>
Enable topology testing with hostpath driver
…ersion_gt Improve snapshot-controller running check and version_gt to support multiple formats
fix syntax for ppc64le build
Improve README by adding an explicit Kubernetes dependency section
This requires adding one more parallel e2e test run with a special focus flag because snapshot tests are still guarded with a "[Feature:VolumeSnapshotDataSource]" tag. The setting that skips all tests with "[Feature:.*]" has to be removed because it overrides the focus. We don't have serial snapshot tests yet. This needs to be modified again if we add any in the future.
Enable snapshot tests in 1.17 to be run in non-alpha jobs.
Signed-off-by: Grant Griffiths <[email protected]>
…netes_fix Fix version_gt to work with Kubernetes prefix
Update prow hostpath driver version to 1.3.0-rc2
Fix overriding of junit results
Signed-off-by: Grant Griffiths <[email protected]>
…rsion_update Update snapshotter to version v2.0.0
Update hostpath driver version to get fix for connection-timeout
Document the process for releasing a new sidecar
fix incorrect link
That this hasn't been done before is an oversight. Apparently it hasn't been a problem because there never have been feature gates that mattered?
This relies on a slightly different deployment script: a "deploy.sh" must exist which knows that it has to dump a test driver configurion into the file pointed to with CSI_PROW_TEST_DRIVER, if that env variable is set. That way, we no longer need to know what capabilities the installed driver has.
k8s-ci-robot
added
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly 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 |
k8s-ci-robot
added
approved
|
@pohly: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
k8s-ci-robot
added
the
needs-rebase
|
@pohly: PR needs rebase. 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. |
|
/close merged via automated PR |
|
@pohly: Closed this PR. 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. |
…go_modules/k8s.io/apimachinery-0.26.1 Bump k8s.io/apimachinery from 0.26.0 to 0.26.1
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This is an experimental PR to try out the changes from kubernetes-csi/csi-driver-host-path#143 in a different sidecar repo.
Which issue(s) this PR fixes:
Related-to: kubernetes-csi/csi-release-tools#32
Does this PR introduce a user-facing change?: