-
Notifications
You must be signed in to change notification settings - Fork 1.5k
feat: add isSameResource on HasMetadata #7426
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
Open
metacosm
wants to merge
3
commits into
main
Choose a base branch
from
is-same-resource
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+173
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Should apiVersion be checked too? (e.g. two resources with same kind but different apiVersion v1beta1 vs. v1alpha1 (or a real legacy case such as apps/v1 vs extensions/v1beta1 Deployment) would be considered the same)
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.
The first implementation was doing that and then I read in the Kube docs that an object's identity shouldn't take the API version into consideration… cf https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
We could have an option to also check the API version, if we think it's interesting to do so.
Another question I had, was with respect to the UID… I'm not sure about how it's used and whether or not it should factor in this function.
Uh oh!
There was an error while loading. Please reload this page.
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, I was just going to ask that, if UID is present on both resources on that case probably would be enough to check that.
Uh oh!
There was an error while loading. Please reload this page.
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.
API version is tricky, since there should be a conversion hook, and there is always just one stored version, not sure if after the conversion it preserves UID, would be worth to check.
Is is a matter of definition too, what we call "same resource".
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 would be a little cautious introducing notions like this which are not generic kubernetes terms
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.
The question I had wrt to UID is that I was wondering if it's possible for a logical resource which would be recreated with the same UID (since it's supposed to be the same resource) could end up with a different name and namespace? I don't really have much experience dealing with UIDs so I'm not too sure if that's a valid use case or not…
Uh oh!
There was an error while loading. Please reload this page.
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.
Here we are comparing two resources where both should live on the server (or at least live close in time), theoretically this could happen, but I don't think we should care. The probability of UID collision is already:
For example, the number of random version 4 UUIDs which need to be generated in order to have a 50% probability of at least one collision is 2.71 quintillion.And we are talking about a short period of time this to happen.
If that happens I will eat my red hat :)
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.
did you manage to check the UID preservation after the conversion hook is applied?
From my side I'm happy to merge this since you folks (and downstream users of JOSDK) are probably the ones who will be consuming it.