enhancements
enhancements copied to clipboard
KEP-3314: Changed Block Tracking With CSI VolumeSnapshotDelta
Signed-off-by: Ivan Sim [email protected]
- One-line PR description: Add new KEP for changed block tracking (CBT)
- Issue link: #3314
- Other comments:
@ihcsim There is a mismatch in the callbackURL format used in DifferentialSnapshot status example in cbt-step-02.png i.e (https://stream-uri:port-number/cr-namespace/cr-name) and cbt-step-03.png which is (https://stream-uri:port-number/custom-resource-uid).
@ihcsim Thanks..! I have few review comments and will pass one more round soon..
/retest
/assign @msau42
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ihcsim
Once this PR has been reviewed and has the lgtm label, please assign johnbelamaric for approval by writing /assign @johnbelamaric in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
I am not sure about usage of the aggregated API server and "virtual resources" there - I can see it is possible to implement it this way, I just don't know if it's the best option. The alternatives are well documented, so we can discuss the details in the API review. The interface between a storage backend, a CSI driver and aggregated API server looks OK.
From storage point of view, this KEP makes sense and is implementable. /lgtm
I let @msau42 approve (or ping me on slack).
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ihcsim
Once this PR has been reviewed and has the lgtm label, please assign johnbelamaric for approval by writing /assign @johnbelamaric in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Looking at commits since my last review, PRR should still be good on this. I just can't do the prow approval until I see the SIG approval.
@thockin @johnbelamaric Thanks for the feedback. The working group still has some concerns on the proposed aggregated API server approach. There is still some work to be done here.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Superseded by https://github.com/kubernetes/enhancements/pull/4082, due to authorship changes.