hello world installation documentation doesn't work about lib-volume-populator HOT 11 OPEN

This worked for me (thanks @nyoxi):

$ kubectl create -f https://raw.githubusercontent.com/kubernetes-csi/volume-data-source-validator/v1.0.1/client/config/crd/populator.storage.k8s.io_volumepopulators.yaml
customresourcedefinition.apiextensions.k8s.io/volumepopulators.populator.storage.k8s.io created
$ kubectl create -f https://raw.githubusercontent.com/kubernetes-csi/volume-data-source-validator/v1.0.1/deploy/kubernetes/rbac-data-source-validator.yaml
serviceaccount/volume-data-source-validator created
clusterrole.rbac.authorization.k8s.io/volume-data-source-validator created
clusterrolebinding.rbac.authorization.k8s.io/volume-data-source-validator created
$ kubectl create -f https://raw.githubusercontent.com/kubernetes-csi/volume-data-source-validator/v1.0.1/deploy/kubernetes/setup-data-source-validator.yaml
statefulset.apps/volume-data-source-validator created
$ kubectl apply -f deploy.yaml 
namespace/hello unchanged
serviceaccount/hello-account unchanged
clusterrole.rbac.authorization.k8s.io/hello-role unchanged
clusterrolebinding.rbac.authorization.k8s.io/hello-binding unchanged
deployment.apps/hello-populator unchanged
volumepopulator.populator.storage.k8s.io/hello-populator created

from lib-volume-populator.

Hi @rwmjones i have tried also and got the same error as
error: resource mapping not found for name: "hello-populator" namespace: "" from "https://raw.githubusercontent.com/kubernetes-csi/lib-volume-populator/master/example/hello-populator/deploy.yaml": no matches for kind "VolumePopulator" in version "populator.storage.k8s.io/v1beta1" ensure CRDs are installed first

should i need to apply separate CRD's also?

from lib-volume-populator.

I just got to know you have deployed corresponding crd's from https://github.com/kubernetes-csi/volume-data-source-validator/tree/master/client/config/crd and it worked for me but not documented in README as you stated in the issue description so is it ok to document those crd's also?

from lib-volume-populator.

We should improve the documentation for the volume-data-source-validator, and we should mention that that project is a pre-req for this example. Alternatively, we can just modify the YAML for this example to not install the VolumePopulator object.

from lib-volume-populator.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from lib-volume-populator.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from lib-volume-populator.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

from lib-volume-populator.

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

from lib-volume-populator.