Add Support for Component Priority Class Configuration in Karmada Operator

[jabellard]

What would you like to be added:
Today, when creating a Karmada instance to be managed by the operator, it's not possible to specify the priority class of the control plane components for that instance. Currently, the priority class name of some of the components is hardcoded as system-node-critical, while other components don't have a priority class specified at all. This feature request is for providing the ability of specifying the priority class of the Karmada control plane components.

Why is this needed:
At Bloomberg, we're currently building a managed Karmada platform and want to use the Karmada operator to manage the entire lifecycle of managed Karmada instances. To ensure reliability and stability of managed Karmada control planes, we would like to have the ability of specifying the priority class of Karmada control plane components.

[jabellard]

Hey @RainbowMango , I just submitted a proposal for this feature.