-
Notifications
You must be signed in to change notification settings - Fork 28
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 metadata propagation on the workload cluster nodes #177
Merged
alexander-demicev
merged 5 commits into
rancher:main
from
Danil-Grigorev:propagate-annotations
Oct 30, 2023
Merged
Implement metadata propagation on the workload cluster nodes #177
alexander-demicev
merged 5 commits into
rancher:main
from
Danil-Grigorev:propagate-annotations
Oct 30, 2023
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
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
20 times, most recently
from
October 16, 2023 15:51
28f4a5c
to
4b2ca55
Compare
Danil-Grigorev
requested review from
belgaied2,
richardcase and
alexander-demicev
October 16, 2023 17:16
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
from
October 17, 2023 09:10
4b2ca55
to
2388fb7
Compare
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, 2 small comments
@Danil-Grigorev - i think that we should update the existing e2e to ensure that the labels and annotations do get propogated to the nodes. |
Also, the DCO check is failing. |
4 tasks
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
from
October 27, 2023 12:45
2388fb7
to
66bca65
Compare
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
4 times, most recently
from
October 27, 2023 13:00
8d6d489
to
352d08a
Compare
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
2 times, most recently
from
October 27, 2023 13:39
d045cb1
to
92999f0
Compare
alexander-demicev
previously approved these changes
Oct 27, 2023
We can add e2e tests in a follow-up PR as discussed with @Danil-Grigorev |
richardcase
reviewed
Oct 27, 2023
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
from
October 30, 2023 13:58
ab9efb9
to
56f4d82
Compare
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
from
October 30, 2023 14:01
56f4d82
to
2ee1647
Compare
alexander-demicev
previously approved these changes
Oct 30, 2023
Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
Danil-Grigorev
force-pushed
the
propagate-annotations
branch
from
October 30, 2023 15:51
2ee1647
to
021c148
Compare
alexander-demicev
approved these changes
Oct 30, 2023
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.
kind/feature
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #155
Special notes for your reviewer:
Checklist: