Error in deploying csi-hostpath-driverinfo.yaml <STDIN - Cant find KIND - CSIDriver> on 15,16 and 17 K8s

[lmcdasm]

Hello.

I have just cloned the repo for the host-path-csi-project:
https://github.com/kubernetes-csi/csi-driver-host-path

i have tried with 15, 16 and now on 17.4 K8S (that is what this log is).

When i do the deployment (again, im using 17+ K8S here instructions here but i got stuck at both places) i get the same error when i do the command:

deploy/kubernetes-latest/deploy.sh

as outlined here: https://github.com/kubernetes-csi/csi-driver-host-path/blob/master/docs/deploy-1.17-and-later.md

ERROR during deployment:
deploying hostpath components
deploy/kubernetes-latest/hostpath/csi-hostpath-attacher.yaml
using image: quay.io/k8scsi/csi-attacher:v3.0.0-rc1
service/csi-hostpath-attacher unchanged
statefulset.apps/csi-hostpath-attacher unchanged
deploy/kubernetes-latest/hostpath/csi-hostpath-driverinfo.yaml
error: unable to recognize "STDIN": no matches for kind "CSIDriver" in version "storage.k8s.io/v1"
modified version of deploy/kubernetes-latest/hostpath/csi-hostpath-driverinfo.yaml:
apiVersion: storage.k8s.io/v1

i have verified that the CRDs are installed and i can see that the api "storage.k8s.io/v1" has a "Kind" CSIDriver (see output of kubectl api-resources).

[dasm@ip-0 csi-driver-host-path]$ kubectl api-resources
volumesnapshotclasses snapshot.storage.k8s.io false VolumeSnapshotClass
volumesnapshotcontents snapshot.storage.k8s.io false VolumeSnapshotContent
volumesnapshots snapshot.storage.k8s.io true VolumeSnapshot
csidrivers storage.k8s.io false CSIDriver
csinodes storage.k8s.io false CSINode
storageclasses sc storage.k8s.io false StorageClass
volumeattachments storage.k8s.io false VolumeAttachment

Here is my K8s version information:

[dasm@ip-0 csi-driver-host-path]$ kubectl version --short
Client Version: v1.18.3
Server Version: v1.17.4
[dasm@ip-0 csi-driver-host-path]$

[pohly]

deploy/kubernetes-latest/deploy.sh is a symlink for the latest deployment, which is currently kubernetes-1.18. That deployment is not compatible with 1.17 because the version of CSIDriver changed from storage.k8s.io/v1beta1 to storage.k8s.io/v1.

If you use the kubernetes-1.17 deployment, it should work.

This probably should be explained better in the instructions if it wasn't clear. If you have suggestions for how it should be worded, then a PR would be welcome.

[lmcdasm]

Hey there. Argh.. i should have just chased down the softlink.. thanks for pointing that out! Cheers, Daniel

…

On Mon, 22 Jun 2020 at 02:37, Patrick Ohly ***@***.***> wrote: deploy/kubernetes-latest/deploy.sh is a symlink for the latest deployment, which is currently kubernetes-1.18. That deployment is not compatible with 1.17 because the version of CSIDriver changed from storage.k8s.io/v1beta1 to storage.k8s.io/v1. If you use the kubernetes-1.17 deployment, it should work. This probably should be explained better in the instructions if it wasn't clear. If you have suggestions for how it should be worded, then a PR would be welcome. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#187 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHMXREADN5ZFXP7O4BEPKLRX33Y7ANCNFSM4ODHAULQ> .

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.