remove service accounts for karmada components except for karmada-agent

[carlory]

Signed-off-by: carlory baofa.fan@daocloud.io

What type of PR is this?

/kind feature

What this PR does / why we need it:

See #2511 (comment)

Which issue(s) this PR fixes:
Part of #2511

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmadactl`/`chart`: The `init` no longer creates redundant ServiceAccounts for components except `karmada-agent`.

[carlory]

/cc @RainbowMango @lonelyCZ

[RainbowMango]

Thanks @carlory , I'll look at it next week.

[RainbowMango]

I just remember that there is an unusual case where they install Karmada on a cluster and take the kube-apiserver as the karmada-apiserver. In that case, does the component needs RBAC?

[carlory]

@RainbowMango

I don't think we should encourage such usage, because two controllers controlling the same resource, kube-controller-manager and karmada-controller-manager, will conflict when updating state.

[carlory]

In that case, does the component needs RBAC?

yes. but we should not support this case, right?

[lonelyCZ]

In that case, does the component needs RBAC?

This should be a custom requirement, we can add a doc to describe it. I think that the standard installation method currently doesn't need them.

[RainbowMango]

This should be a custom requirement, we can add a doc to describe it. I think that the standard installation method currently doesn't need them.

Good point.

[RainbowMango]

/lgtm
/approve

Note: I updated the release note a little bit.

[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:

• OWNERS [RainbowMango]

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