support config karmada components resources

[wawa0210]

What type of PR is this?

/kind feature

What this PR does / why we need it:

The karmada operator does not support users to explicitly set the resource scale of each component. But resource planning will be different in different scenarios, so we can provide explicit configuration

Which issue(s) this PR fixes:
from #3732 (comment)

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmada-operator`: Support config required resources for each Karmada component.

Test Results

karmada instance yaml with resources config

apiVersion: operator.karmada.io/v1alpha1
kind: Karmada
metadata:
  name: karmada-demo
  namespace: test
spec:
  components:
    etcd:
      local:
        imageRepository: k8s.m.daocloud.io/etcd
        imageTag: 3.5.9-0
        replicas: 1
        resources:
          requests:
            cpu: 216m
    karmadaMetricsAdapter:
      resources:
        requests:
          cpu: 111m
    karmadaAPIServer:
      imageRepository: k8s.m.daocloud.io/kube-apiserver
      imageTag: v1.25.4
      replicas: 1
      serviceType: NodePort
      serviceSubnet: 10.96.0.0/12
      resources:
        requests:
          cpu: 276m
    karmadaAggregatedAPIServer:
      imageRepository: docker.io/karmada/karmada-aggregated-apiserver
      imageTag: v1.6.0
      replicas: 1
      resources:
        requests:
          cpu: 279m
    karmadaControllerManager:
      imageRepository: docker.io/karmada/karmada-controller-manager
      imageTag: v1.6.0
      replicas: 1
      resources:
        requests:
          cpu: 290m
    karmadaScheduler:
      imageRepository: docker.io/karmada/karmada-scheduler
      imageTag: v1.6.0
      replicas: 1
      resources:
        requests:
          cpu: 370m
    karmadaWebhook:
      imageRepository: docker.io/karmada/karmada-webhook
      imageTag: v1.6.0
      replicas: 1
      resources:
        requests:
          cpu: 470m
    kubeControllerManager:
      imageRepository: k8s.m.daocloud.io/kube-controller-manager
      imageTag: v1.25.4
      replicas: 1
      resources:
        requests:
          cpu: 550m

actual effect

➜  karmada git:(support-config-karmada-component-resources) ✗ kubectl get karmada -n test
NAME            READY   AGE
karmada-demo   True    27m


➜  karmada git:(support-config-karmada-component-resources) ✗ kubectl get po -n test  -w
NAME                                                     READY   STATUS    RESTARTS   AGE
karmada-demo-aggregated-apiserver-f4b494875-5xwkf       1/1     Running   0          24m
karmada-demo-apiserver-579bd4875f-26bpn                 1/1     Running   0          25m
karmada-demo1-controller-manager-5f5fb98c4-448lc         1/1     Running   0          24m
karmada-demo-etcd-0                                     1/1     Running   0          25m
karmada-demo-kube-controller-manager-5b8bfdd9fd-psbq7   1/1     Running   0          24m
karmada-demo-metrics-adapter-98dbbdc79-4djc5            1/1     Running   0          24m
karmada-demo-metrics-adapter-98dbbdc79-xbhwq            1/1     Running   0          24m
karmada-demo-scheduler-bf6fc95c5-tz2q6                  1/1     Running   0          24m
karmada-demo-webhook-84d87598d6-xtlmq                   1/1     Running   0          24m

# grep the resources(The number is consistent with the number of karmada instance components)

➜  karmada git:(support-config-karmada-component-resources) ✗ kubectl get po -n test  -o yaml | grep -A 2 resources
      resources:
        requests:
          cpu: 279m
--
      resources:
        requests:
          cpu: 276m
--
      resources:
        requests:
          cpu: 290m
--
      resources:
        requests:
          cpu: 216m
--
      resources:
        requests:
          cpu: 550m
--
      resources:
        requests:
          cpu: 111m
--
      resources:
        requests:
          cpu: 111m
--
      resources:
        requests:
          cpu: 370m
--
      resources:
        requests:
          cpu: 470m

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: +0.02% 🎉

Comparison is base (244c73c) 53.82% compared to head (3d7619d) 53.84%.
Report is 4 commits behind head on master.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4059      +/-   ##
==========================================
+ Coverage   53.82%   53.84%   +0.02%     
==========================================
  Files         231      231              
  Lines       23013    23013              
==========================================
+ Hits        12386    12391       +5     
+ Misses       9954     9950       -4     
+ Partials      673      672       -1     

Flag	Coverage Δ
unittests	53.84% <ø> (+0.02%)	⬆️

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

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[calvin0327]

It looks good. @jwcesign @RainbowMango PTAL

/lgtm

[RainbowMango]

Just noticed that you are using your Chinese name in your commit:

Author: 张潇 <[email protected]>
Date:   Wed Sep 13 18:09:23 2023 +0800

    support config karmada components resources

    Signed-off-by: 张潇 <[email protected]>

I'm not sure if GitHub or CNCF tools could count your contribution. This is concerning.

[wawa0210]

Just noticed that you are using your Chinese name in your commit:

Author: 张潇 <[email protected]>
Date:   Wed Sep 13 18:09:23 2023 +0800

    support config karmada components resources

    Signed-off-by: 张潇 <[email protected]>

I'm not sure if GitHub or CNCF tools could count your contribution. This is concerning.

I recently changed my computer and I checked and it shouldn't be affected. I revised it again， thx

[RainbowMango]

/lgtm
/approve

Thanks.

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

• operator/OWNERS [RainbowMango]

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