Grant karmada-agent permission to access resourceinterpretercustomizations

[jwcesign]

Signed-off-by: jwcesign jiangwei115@huawei.com

What type of PR is this?
/kind bug

What this PR does / why we need it:

• Grant karmada-agent permission to acccess resourceinterpretercustomizations

Which issue(s) this PR fixes:
Fixes #2982

Special notes for your reviewer:
none

Does this PR introduce a user-facing change?:

`karmadactl init`: Grant karmada-agent permission to access resourceinterpretercustomizations.

[jwcesign]

cc @XiShanYongYe-Chang @lonelyCZ

[codecov-commenter]

Codecov Report

Merging #2984 (c174728) into master (9068240) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #2984   +/-   ##
=======================================
  Coverage   38.58%   38.58%           
=======================================
  Files         206      206           
  Lines       18820    18820           
=======================================
  Hits         7261     7261           
  Misses      11129    11129           
  Partials      430      430           

Flag	Coverage Δ
unittests	38.58% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
pkg/karmadactl/cmdinit/karmada/rbac.go	88.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[XiShanYongYe-Chang]

LGTM

[lonelyCZ]

Thanks @jwcesign , have you tested it in your env?

And please update the release-note to

`karmadactl init`: Grant karmada-agent permission to access resourceinterpretercustomizations.

and it could be cherry-picked to release-1.4 after merged.

[jwcesign]

Thanks @jwcesign , have you tested it in your env?

And please update the release-note to

`karmadactl init`: Grant karmada-agent permission to access resourceinterpretercustomizations.

and it could be cherry-picked to release-1.4 after merged.

Updated.
Yeah, I tested it, and it works fine and the error has gone. The log now looks like:

I1221 07:04:38.167481       1 reflector.go:559] k8s.io/client-go/informers/factory.go:134: Watch close - *v1.Pod total 7 items received
I1221 07:04:38.232763       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:04:48.242501       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:04:58.253555       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:05:08.264764       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:05:18.273936       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:05:28.283229       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:05:38.051841       1 reflector.go:559] k8s.io/client-go/dynamic/dynamicinformer/informer.go:91: Watch close - *unstructured.Unstructured total 0 items received
I1221 07:05:38.292174       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:05:48.301247       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:05:58.311827       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:06:08.325698       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:06:18.335299       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:06:28.345986       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:06:38.360336       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:06:48.370071       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:06:58.381978       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:07:01.166452       1 reflector.go:559] k8s.io/client-go/informers/factory.go:134: Watch close - *v1.Node total 13 items received
I1221 07:07:06.431935       1 reflector.go:559] k8s.io/client-go/dynamic/dynamicinformer/informer.go:91: Watch close - *unstructured.Unstructured total 9 items received
I1221 07:07:08.394397       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:07:18.407074       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member
I1221 07:07:28.422169       1 cluster_status_controller.go:109] Syncing cluster status: kind-karmada-member

[RainbowMango]

Have we granted permission to karmada-controller-manager as well?

[lonelyCZ]

Have we granted permission to karmada-controller-manager as well?

karmada-controller-manager seemingly have all permissions.

[lonelyCZ]

/lgtm

[RainbowMango]

/approve

[karmada-bot]

[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

Needs approval from an approver in each of these files:

• pkg/karmadactl/cmdinit/OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment