-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Document pod-template-hash label #3876
Conversation
@Kargakis Since you mention 1.7, is this for the 1.7 release? If so, I'm going to tag it w/ the 1.7 Milestone and move it to the |
|
Do users need to know about the |
|
Ok, then I would be inclined to put this in the developer docs. @janetkuo Can you suggest a location? Thx |
@Kargakis If you agree, then I will close this PR. |
The fact that users are confused with this label and ask questions about it, warrants adding a section in user docs. |
Well, if users are asking questions about it, I don't see the harm in having it in the user docs as well. |
@chenopis can we move forward with this one? |
@chenopis ping |
Sorry for the delay, taking a look now |
ReplicaSets of a Deployment will not overlap among them. It is computed by hashing the PodTemplate of the ReplicaSet | ||
and using the resulting hash as the label value that will be added in the ReplicaSet selector, pod template labels, | ||
and in any existing Pods that the ReplicaSet may have. Up until 1.6, the hashing algorithm that is used is adler. | ||
Starting from 1.7, we switch to a more stable algorithm, fnv, and also introduce a hashing collision avoidance |
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.
Remove the hash algorithm part, since it's implementation detail.
Starting from 1.7, we switch to a more stable algorithm, fnv, and also introduce a hashing collision avoidance | ||
mechanism which will help in ensuring that Deployments are not going to be plagued by hashing collisions anymore. | ||
|
||
**Note:** This label is not meant to be updated or removed by users! |
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.
Maybe move this to be the first sentence of this section? The first thing users need to know is that this label is generated by the server, is essential, and should not be mutated by the users. Then we can talk about details of the label later.
Signed-off-by: Michail Kargakis <mkargaki@redhat.com>
I'm good w/ this. Once @janetkuo gives the tech lgtm, I will merge it. |
Fixes #3569
@kubernetes/sig-apps-misc
This change is