Support full strategic merge patch #25
Labels
area/control-plane
Control plane related
kind/enhancement
Enhancement, improvement, extension
lifecycle/icebox
Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.)
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
status/closed
Issue is closed (either delivered or triaged)
What would you like to be added:
If there is a conflict between the scheduling criteria (potentially more than one) being injected and what is already present in the target pod spec/template, merge done by kupid is currently ad hoc.
It is desirable to support full strategic merge patch in such a cases.
Why is this needed:
Consistency with Kubernetes best-practicies.
The text was updated successfully, but these errors were encountered: