community binary is missing

[msau42]

Whenever there's a new CSI Proxy proxy release there's no post-release action that makes the binary available to use.

[msau42]

/assign @jingxu97

[msau42]

fyi csi proxy build job has been disabled until this is fixed: https://github.com/kubernetes/test-infra/pull/19937

[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-contributor-experience at kubernetes/community. /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-contributor-experience at kubernetes/community. /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-contributor-experience at kubernetes/community. /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-contributor-experience at kubernetes/community. /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.

[msau42]

/reopen

Discussed with wg-k8s-infra. There's no automatic promotion process from staging to release. A sig-lead will have to do it.

[k8s-ci-robot]

@msau42: Reopened this issue.

In response to this:

/reopen

Discussed with wg-k8s-infra. There's no automatic promotion process from staging to release. A sig-lead will have to do it.

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.

[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-contributor-experience at kubernetes/community. /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-contributor-experience at kubernetes/community. /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.

[msau42]

/reopen

This is still outstanding

[k8s-ci-robot]

@msau42: Reopened this issue.

In response to this:

/reopen

This is still outstanding

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.

[jingxu97]

trying to work on make versioned information when uploading to gcs for csi proxy binary

[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-contributor-experience at kubernetes/community. /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-contributor-experience at kubernetes/community. /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.

[mauriciopoppe]

/reopen @jingxu97 this was closed automatically, can we close it now that https://github.com/kubernetes-csi/csi-proxy/pull/148 is merged?

[k8s-ci-robot]

@mauriciopoppe: Reopened this issue.

In response to this:

/reopen @jingxu97 this was closed automatically, can we close it now that https://github.com/kubernetes-csi/csi-proxy/pull/148 is merged?

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.

[k8s-triage-robot]

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-contributor-experience at kubernetes/community. /close

[k8s-ci-robot]

@k8s-triage-robot: 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-contributor-experience at kubernetes/community. /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.

[msau42]

/reopen

[k8s-ci-robot]

@msau42: Reopened this issue.

In response to this:

/reopen

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.

[msau42]

/remove-lifecycle rotten

[msau42]

@jingxu97 what's the status on this?

[mauriciopoppe]

I saw that #148 is working as expected, on post submit cloudbuild is pushing the binary to gs://k8s-staging-sig-storage/csi-proxy/<tag>/

gsutil ls gs://k8s-staging-sig-storage/csi-proxy/
gs://k8s-staging-sig-storage/csi-proxy/artifacts-3c1563ce-8208-4b4e-913e-035a72f4eeba.json
gs://k8s-staging-sig-storage/csi-proxy/artifacts-43e1de7f-3d90-4d9b-b6dd-91498d4292a0.json
gs://k8s-staging-sig-storage/csi-proxy/artifacts-c56099a1-2675-4807-b86a-291da2ccda79.json
gs://k8s-staging-sig-storage/csi-proxy/artifacts-d1bb985f-4fcc-42a9-8d8c-c3140f456f9a.json
gs://k8s-staging-sig-storage/csi-proxy/csi-proxy-master.exe
gs://k8s-staging-sig-storage/csi-proxy/csi-proxy-v1.0.0-rc.1.exe
gs://k8s-staging-sig-storage/csi-proxy/master/
gs://k8s-staging-sig-storage/csi-proxy/release-1.0/
gs://k8s-staging-sig-storage/csi-proxy/v1.0.0/
gs://k8s-staging-sig-storage/csi-proxy/v1.0.1/

However @jingxu97 mentioned that what's missing is copying these artifacts to the release/prod bucket which might be a manual process

[k8s-triage-robot]

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

[k8s-triage-robot]

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

[mauriciopoppe]

/remove-lifecycle rotten

[divyenpatel]

@jingxu97 we are planning to release vSphere CSI Driver with windows support using CSI proxy. When do you think we will have the binarily available for customer documentation?

customers need the verified binary for the installation of csi-proxy.

cc: @xing-yang

[k8s-triage-robot]

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

[k8s-triage-robot]

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