Daemonset deployment failing - ImagePullBackOff about csi-proxy HOT 7 CLOSED

Thanks for the report! Our README looks like it's out of date, the sig storage images were changed to be served from a different location, please use k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0, org/csi-driver:win-v1 should be the driver that you want to deploy on your cluster e.g. for the GCE PD CSI Driver gke.gcr.io/gcp-compute-persistent-disk-csi-driver

from csi-proxy.

Thanks, it worked.
Now I'm receiving the following error on the csi-driver-registrar:

processstarttime.go:43] Could not get process start time, could not read /proc: CreateFile /proc: The system cannot find the file specified.

Log attached.
csi-driver-registrar.txt

from csi-proxy.

The README has a sample implementation with some placeholders (although the placeholders are not very well defined), I think it depends on how this sidecar is used in your driver, for example the configuration for GCE PD CSI driver in windows nodes is https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/deploy/kubernetes/base/node_windows/node.yaml

from csi-proxy.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

from csi-proxy.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

from csi-proxy.

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

This bot triages issues and PRs 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 or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

from csi-proxy.

@k8s-triage-robot: Closing this issue.

from csi-proxy.