Closed a7i closed 3 weeks ago
Attention: Patch coverage is 35.00000%
with 13 lines
in your changes are missing coverage. Please review.
Project coverage is 51.79%. Comparing base (
ff7322a
) to head (ae9f508
).
Files | Patch % | Lines |
---|---|---|
pkg/resourceinterpreter/default/native/retain.go | 35.00% | 9 Missing and 4 partials :warning: |
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
You can add the component name karmada-controller-manager
to the release-note.
The retain logic is modified in the current PR. However, retain is used when resources in member clusters are updated. If resources are created, will the UID and token information in the secret on the control plane be carried to the member cluster?
Kindly ping @a7i
@XiShanYongYe-Chang Yes it will but we observed in our case that the member cluster kube-controller-manager will fix up the values and get ignored by karmada on update.
Is there a "global" level ignore for CREATE as well?
Maybe we can do it in the karmada-webhook
:
@XiShanYongYe-Chang done, I kept as two separate commits for easier review. Happy to rebase and squash if needed.
It occurs a lint error:
pkg/resourceinterpreter/default/native/prune/prune.go:33:1: cyclomatic complexity 18 of func `RemoveIrrelevantField` is high (> 15) (gocyclo)
@XiShanYongYe-Chang let me take a stab at refactoring this function in a separate PR and I'll come back to this after that's reviewed/merged
Hi @a7i, CI errors may prevent PRs from being merged.
Hi @a7i, CI errors may prevent PRs from being merged.
I understand, hence why I'm suggesting to put a hold on this PR, until we refactor this function first (in a separate PR).
I understand, hence why I'm suggesting to put a hold on this PR, until we refactor this function first (in a separate PR).
Thanks @a7i, I got it :)
Hi @a7i , now we can go on this PR.
LGTM Thanks for your quick response!
But would you mind squash commits?
LGTM Thanks for your quick response!
But would you mind squash commits?
I do not mind at all! Was keeping them separate for easier review
haha, your code is so clear that I don't have to review it by commits~
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: RainbowMango
The full list of commands accepted by this bot can be found here.
The pull request process is described here
gonna heading home now, good morning to you
gonna heading home now, good morning to you
long day! I appreciate the thorough review and all the great feedback 🎉
I really really hope people like you join us in maintaining this project, can we get started from the org membership?
Hi @RainbowMango and @XiShanYongYe-Chang I hope you would consider sponsoring me ❤️
I have verified that my sponsors are from different member companies
perhaps @chaunceyjiang would consider 🙇🏼
Hi @RainbowMango and @XiShanYongYe-Chang I hope you would consider sponsoring me ❤️
definitly!
What type of PR is this?
/kind feature
What this PR does / why we need it: Prior to kubernetes 1.24, Kubernetes controller-manager automatically created a Secret (with a long-lived token). Starting with 1.24, in order to create a Secret with long-lived token, you have to manually create a Secret and link it to the Service Account. Karmada currently doesn't support propagating this Secret as it is explicitly disabled.
Which issue(s) this PR fixes: Fixes #4752
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Yes