-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implement writebuffer #8
Conversation
I haven't read through all the code, so this might be addressed there: How do we ensure we don't read before these async ops are committed? Is this where the informer cache abstraction comes in? |
The logic to determine if a write is needed is itself pushed onto the write queue. So we don't read from back in time relative to the write i.e. the controller that writes the status doesn't read it. |
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.
LGTM! 🚢
Adds the first bit of code in the reconstitution package that will be responsible for handling each element of
ResourceSlice
s as individual resources.