Restrict supported service types of Karamda APIServer supported by karmada-operator #5769
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 cleanup
/kind api-change
What this PR does / why we need it:
This PR restrics the service types supported by karmada-operator.
Which issue(s) this PR fixes:
Part of #5767
Special notes for your reviewer:
This PR introduces validation rules which narrow down the range of acceptable configuration, but this has no impact on users who are currently using
ClusterIP
andNodePort
. And forLoadbalancer
andExternalName
, currently not supported. (We are considering introduce the support ofLoadbalancer
to address the use case reported at #4634).Does this PR introduce a user-facing change?: