Controller is unresponsive to context cancellation passed to Run(ctx context.Context)

[MatthiasWerning]

It seems to me that the provisioning controller does not react to any context cancellation that was passed down the chain from the calling application / library.

This is probably due to the select {} statement in line 862 of controller/controller.go. Thus the claimQueue and volumeQueue will effectively never be shutdown since the local run(ctx context.Context) function never returns (with exception to an unsuccessful cache sync await).

Would be great if this could be fixed in v8 as well. This probably just requires the select {} to be replaced by <-ctx.Done() as far as I tried it using my own provisioning controller.

[jsafrane]

@MatthiasWerning do you mind sending a pull request? Master first, but we can fix release-8.0 too.

[k8s-triage-robot]

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

[MatthiasWerning]

Closed in favor of #159