standardize the naming of karmada secrets

[husnialhamdani]

What type of PR is this?

What this PR does / why we need it:

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

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[karmada-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lonelycz for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• operator/OWNERS

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

[husnialhamdani]

actually, in this sub task we need to do just two things:

1. the yaml manifest of each component is listed in operator/pkg/controlplane/ directory, we shall improve the yaml manifest according to above example
2. the certificate is generated in NewCertTask and stored to secret in NewUploadCertsTask, we will rename the secret and the field according to above new naming convention.

Am I doing right, so far?
At least for point number 1

@chaosi-zju

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.95%. Comparing base (3b6c0e0) to head (b82a6a2).

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

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6178      +/-   ##
==========================================
- Coverage   47.95%   47.95%   -0.01%     
==========================================
  Files         674      674              
  Lines       55841    55841              
==========================================
- Hits        26781    26776       -5     
- Misses      27311    27315       +4     
- Partials     1749     1750       +1     

Flag	Coverage Δ
unittests	47.95% <ø> (-0.01%)	⬇️

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.

[chaosi-zju]

sorry for late

Am I doing right, so far? At least for point number 1

yes, as for point number 1, you are on the right track.

the next steps you should do are:

1. update the volumes and volumeMounts field for these componets like standardize the naming of karmada secrets in local up method #5423, because these cert files are now mounted from defferent secret~
2. for other components, also improve this part of the modification.

then you may achieve point number 1, this part is not too complicated, you can do it boldly~

[husnialhamdani]

1. the yaml manifest of each component is listed in operator/pkg/controlplane/ directory, we shall improve the yaml manifest according to above example
2. the certificate is generated in NewCertTask and stored to secret in NewUploadCertsTask, we will rename the secret and the field according to above new naming convention.

Sure let me finalize for point number 1, but I'm confused on how to rename the secret, could you give me an example

[chaosi-zju]

Sure let me finalize for point number 1, but I'm confused on how to rename the secret, could you give me an example

Don't worry, let's take it step by step, and complete the point number 1 first.

ps: I'm very sorry for the slow reply because I've been busy with other things recently.