This proposal is about synchronizing the standardization of Karmada's self-signed certificates to other deployment methods.

I previously worked on an LFX project that focused on designing a new certificate signing method for Karmada cluster components. The main idea was to manage the O field for each component's client and server certificates separately, with each component's common name (CN) set to its own unique value.

This project was initially implemented as an early demo, primarily within a bash script used in testing environments. After some time, it seems this change is stable. Could we now try to synchronize this change to other deployment methods?

I am hoping to get some feedback and guidance from the community on this. If possible, I would be very interested in contributing to this effort.

What would you like to be added:
Synchronize the certificate issuance and storage operations from the Karmada bash script deployment method to other deployment methods.
Why is this needed:
Unify the certificate format and storage scheme for different Karmada components and standardize the content of Karmada component certificates.