kubernetes-sigs/kustomize
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kustomize.git synced 2026-06-12 01:14:22 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

fix motivation, this function is scoped edit

Browse Source
This commit is contained in:
koba1t
2022-04-08 04:08:27 +09:00
parent f866701088
commit 32a78f3915
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
proposals/22-03-value-in-the-structured-data.md
View File

@@ -45,8 +45,10 @@ This proposal decides the interfaces to change values in the structured data (li
If this proposal is an expansion of an existing GitHub issue, link to it here.
-->
Fields in Kubernetes objects sometimes include values formatted by structured data like json and yaml substrings in a string literal.
kustomize can strong patch with Kubernetes objects, but kustomize can't manipulate one value on structured, formatted data in the Kubernetes object's string literal field. This is a expected behavior, but kustomize will be very helpful if it can change the value structured data like json and yaml substrings in a string literal.
kustomize can strong patch to Kubernetes objects (yaml file in most cases) with structured edit. And, It is structured data.
Sometimes structured multi-line or long single line string (ex. json,yaml, and other structured format data) is injected in Kubernetes objects' string literal field. And, kustomize seems it only string literal.
So, kustomize can't manipulate one value on structured, formatted data in the Kubernetes object's string literal field. This function is expected behavior, but kustomize will be very helpful if it can change the value of structured data like json and yaml substrings in a string literal.
Eventually, kustomize doesn't support unstructured edits for string literal. The proposal allows editing of an unstructured string literal as an exception if the string literal is a structured string of a well-known format like json.
For example, kustomize can't change the value `"REPLACE_TARGET_HOSTNAME"` in this yaml file straightforwardly.