K8SPXC-1461: improve pvc resize logs #1947
Open
+35
−19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://perconadev.atlassian.net/browse/K8SPXC-1461
DESCRIPTION
Problem:
In situations where storage resources are limited and we attempt to resize PVCs, some PVCs may be successfully resized while others fail. In this case, we log only the PVCs that failed to resize, without logging the PVCs that were resized successfully.
Solution:
Create a warning
Event
onexceeded quota
andstorageclass that provisions the pvc must support resize
errors for each failed PVC update. The operator will depend on these events to get information about each PVC resize failure. The operator should wait until all PVC resize operations are either completed or failed, ensuring that all PVC resize results are logged. Only then, it should revert the PVC size in thecr.yaml
.CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
compare/*-oc.yml
)?Config/Logging/Testability