Skip to content

Pre-stop hook to delete registration socket isn't working #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
verult opened this issue Aug 5, 2019 · 9 comments
Closed

Pre-stop hook to delete registration socket isn't working #365

verult opened this issue Aug 5, 2019 · 9 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone

Comments

@verult
Copy link
Contributor

verult commented Aug 5, 2019

Node-driver-registrar moved to distroless, so shelling no longer works. Alternative solution is being discussed at the node-driver-registrar level here: kubernetes-csi/node-driver-registrar#21 (comment)

@davidz627 davidz627 added this to the GA milestone Sep 18, 2019
@davidz627
Copy link
Contributor

will be fixed in node driver registrar by reconciling the socket and also deleting it on sigterm

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 17, 2019
@verult
Copy link
Contributor Author

verult commented Dec 18, 2019

Issue tracking socket reconciliation:
kubernetes-csi/node-driver-registrar#57

@verult
Copy link
Contributor Author

verult commented Dec 18, 2019

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2019
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 17, 2020
@msau42
Copy link
Contributor

msau42 commented Mar 17, 2020

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 17, 2020
@jsafrane
Copy link
Contributor

I'm removing preStop hook from csi-driver-hostpath in kubernetes-csi/csi-driver-host-path#176. It can't work and nobody is adding shell to node-driver-registrar. It would be nice if it was removed from GCE PD manifests too, so kubernetes tests logs are cleaner.

Effort to add signal handling to node-driver-registrar is IMO orthogonal.

@saad-ali
Copy link
Contributor

saad-ali commented Jul 29, 2020

preStop hook was removed in #520
Whenever kubernetes-csi/node-driver-registrar#21 or kubernetes-csi/node-driver-registrar#57 are tracking the new fix.

@k8s-ci-robot
Copy link
Contributor

@saad-ali: Closing this issue.

In response to this:

preStop hook was removed in #520
Whenever kubernetes-csi/node-driver-registrar#21 or kubernetes-csi/node-driver-registrar#57 are tracking the new fix.

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

7 participants