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

fix(customresources): use a 3-way merge patch instead of strategic merge #1094

Closed
wants to merge 1 commit into from

Conversation

metral
Copy link
Contributor

@metral metral commented May 4, 2020

Proposed changes

CustomResources do not support JSON strategic merges on patch updates.

Instead, they require a JSON 3-way merge patch to properly apply the patch.

CustomResource kinds now are treated separately from other known k8s kinds in
order to apply the proper patch.

A new CoreOS prometheus-operator test with a step update is included to validate this update path.

Related issues (optional)

Fixes #1061

CustomResources do not support [JSON strategic merges](https://tools.ietf.org/html/rfc6902) on patch updates.

Instead, they require a [JSON 3-way merge patch](https://tools.ietf.org/html/rfc7386) to properly apply the patch.

CustomResource kinds now are treated separately from other known k8s kinds in
order to apply the proper patch.

A new [CoreOS prometheus-operator](https://github.com/coreos/prometheus-operator) test with a step update is included to validate this update path.
@metral metral closed this May 4, 2020
@metral
Copy link
Contributor Author

metral commented May 4, 2020

closed in favor of #1095

@metral metral deleted the metral/cr-merge-patch branch May 4, 2020 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CustomResource kinds fail to update
1 participant