You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ProblemStatement: There are kubernetes resources whose specs may consist of fields with type []map[string]interface{}. This is commonly known as list map in Kubernetes world. The current server side apply logic present in metacontroller merges such types based on known merge fields. However, there are cases when known merge fields is not enough. This issue will track the required enhancement to provide custom merge fields that can be used during server side apply.
Take for example following yaml specs that does not merged by metacontroller's current logic. The entire list is treated as an atomic value and is simply replaced with the desired list during a server side apply.
AmitKumarDas
changed the title
add merge strategy to merge states while applying server side apply
add merge strategy to merge states during server side apply
Jun 18, 2020
ProblemStatement: There are kubernetes resources whose specs may consist of fields with type
[]map[string]interface{}
. This is commonly known as list map in Kubernetes world. The currentserver side apply
logic present in metacontroller merges such types based on known merge fields. However, there are cases whenknown merge fields
is not enough. This issue will track the required enhancement to provide custom merge fields that can be used during server side apply.Take for example following yaml specs that does not merged by metacontroller's current logic. The entire list is treated as an atomic value and is simply replaced with the desired list during a server side apply.
Refer:
The text was updated successfully, but these errors were encountered: