add resources to webhook chart

[yizhang-zen]

What type of PR is this?

What this PR does / why we need it:

• add resources to webhook chart
• add descheduler as part of container's name

Does webhook need livenessProbe?

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[calvin0327]

/assign

[calvin0327]

@yizhang-zen Do you test this change?

[yizhang-zen]

@yizhang-zen Do you test this change?

No, I didn't. What are the steps to test out?

[chaosi-zju]

Hello, thank you for your pull request~

1. I wanna to known why you want to add descheduler as part of container's name? Are there any scenes that must be like this?

2. If you want to test this change, I think you can refer to Installing the chart and test it by local installation, then you shall observe if the installation was successful and whether the rename and add resource op done as you expected.

3. I really appreciate it that you add the resources to the chart, further more, it seems like the same bug exist in karmada-scheduler-estimator, could you please help us to fix it too?

Best wishes~

[yizhang-zen]

Thank you, @chaosi-zju

I wanna to known why you want to add descheduler as part of container's name? Are there any scenes that must be like this?

No, just keep the same name output as other components' chart (aggregated apiserver and karmada apiserver for example).

it seems like the same bug exist in karmada-scheduler-estimator, could you please help us to fix it too?

Added:)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c2989cc) 51.87% compared to head (5e89dbb) 51.86%.
Report is 2 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    #3891      +/-   ##
==========================================
- Coverage   51.87%   51.86%   -0.02%     
==========================================
  Files         243      243              
  Lines       24112    24112              
==========================================
- Hits        12509    12506       -3     
- Misses      10921    10923       +2     
- Partials      682      683       +1     

Flag	Coverage Δ
unittests	51.86% <ø> (-0.02%)	⬇️

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

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

[RainbowMango]

@chaosi-zju can you help to take a look at this PR. This reminds me we should enable chart installation in CI.

@yizhang-zen I'm sorry for letting this PR wait so long. Can you help to rebase your PR? Because the test suites now might be different from the master branch.

[yizhang-zen]

@yizhang-zen I'm sorry for letting this PR wait so long. Can you help to rebase your PR? Because the test suites now might be different from the master branch.

You are good. I updated my pr just recently and this is not urgent at all.
I have rebased my PR

[RainbowMango]

/approve

Leave LGTM to chart owners to take another look.

[RainbowMango]

/assign @chaosi-zju @calvin0327

[chaosi-zju]

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

• charts/OWNERS [RainbowMango]

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