Closed jakobmoellerdev closed 1 month ago
Welcome @jakobmoellerdev!
It looks like this is your first PR to kubernetes-csi/external-resizer 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-csi/external-resizer has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @jakobmoellerdev. Thanks for your PR.
I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jakobmoellerdev, jsafrane
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What type of PR is this?
What this PR does / why we need it:
When doing a CSI call to ExpandVolume, external-resizer tries to update the PVC with
FilesystemResizeRequired
. Usually this works fine, however, in case of a PVC conflict, the external-resizer emits an event on the PVC withVolumeResizeFailed
. This event is misleading because the Resize did not actually fail, merely the update to the PVC as requiring the Resize failed. Since this will almost always (unless we face endless races) recover gracefully for conflicts, we should avoid sending the event in this case, and rather recover normally. The logs will still emit a sync failure so admins will still be able to notice races, the event will just no longer be published.Here is an example we collected during test runs in the downstream CSI driver TopoLVM:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: