Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add merge strategy to merge states during server side apply #148

Open
AmitKumarDas opened this issue Jun 18, 2020 · 0 comments
Open

add merge strategy to merge states during server side apply #148

AmitKumarDas opened this issue Jun 18, 2020 · 0 comments

Comments

@AmitKumarDas
Copy link
Owner

AmitKumarDas commented 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 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.

kind: MyResource
spec:
  options:
  - deviceName: abc
    deviceID: abc-101
  - deviceName: def
    deviceID: abc-102

Refer:

@AmitKumarDas 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant