-
Notifications
You must be signed in to change notification settings - Fork 366
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
✨ 📖 tmc: storage docs and apis #1971
✨ 📖 tmc: storage docs and apis #1971
Conversation
Hi @guymguym. Thanks for your PR. I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
@guymguym just bumping this with Andy's suggestions |
/lgtm |
/hold |
c9cb9dc
to
aafd6f9
Compare
d1a3755
to
b1994d3
Compare
/unhold |
Hey @davidfestal @sttts @ncdc |
b1994d3
to
7d6ef9e
Compare
docs/locations-and-scheduling.md
Outdated
This is the case with storage PVs, which are created on the workload cluster by a CSI driver. | ||
|
||
Unlike the `Sync` state, the `Upsync` state is exclusive, and only a single cluster can be upsyncing a resource to KCP. | ||
In addition, other clusters cannot be syncing down while the resource is upsyncing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is "clusters" here? Workspace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok I see the confusion, perhaps in this context it would be better to say "syncers"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's why I was asking - confusion 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does "syncers" help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ncdc I reviewed today with @davidfestal and I think we resolved the confusion around my free use for the term "cluster".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed many occurences to SyncTarget and some others to pcluster. I hope that pcluster is a good term to represent the infrastructure aspects of the downstream cluster.
59b5e43
to
4c979fb
Compare
Signed-off-by: Guy Margalit <guymguym@gmail.com>
Signed-off-by: Guy Margalit <guymguym@gmail.com>
Signed-off-by: Guy Margalit <guymguym@gmail.com>
4c979fb
to
6979131
Compare
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidfestal, sttts The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Guy Margalit guymguym@gmail.com
Summary
This is the first story of the storage epic - kcp-dev/contrib-tmc#112
Related issue(s)