Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind api-change
/kind deprecation
What this PR does / why we need it
Karmada components offer a multitude of customizable features through flags, such as feature gates, allowing users to tailor their Karmada cluster according to their specific needs. Currently, the karmada-operator supports implementing these functionalities via fields like
extraArgs
, but:API
spec.featuregates
,spec.components.<component>.featureGates
andspec.components.<component>.extraArgs
all can be used to customize the component's featureGates. However, an excess of configurable options can confuse users and present challenges for future code maintenance.Component
local etcd
does not support the aforementioned capabilities.The previous implementation has some legacy items.
Based on these considerations, I referred to the
kubeadm
implementation and made modifications to it.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: