🌱 cache: replication controller: attach the shard annotation during object creation #2122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ect creation to avoid an additional UPDATE request, mismatch on the Generation, CreationTime or UID field, replicated objects will have those fields set. by setting the shard name during object creation we instruct the cache server to stop updating/changing those fields in any way. in addition to that, the cache server will remove the annotation before persisting the object because a shard name is calculated based on the storage prefix.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
openshift-ci
bot
added
the
approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
to avoid an additional UPDATE request, mismatch on the Generation, CreationTime or UID field, replicated objects will have those fields set. by setting the shard name during object creation we instruct the cache server to stop updating/changing those fields in any way. in addition to that, the cache server will remove the annotation before persisting the object because a shard name is calculated based on the storage prefix.
Related issue(s)
requires kcp-dev/kubernetes#106 and kcp-dev/kubernetes#107
part of #342