🔀 Merger 🔀

A Kustomize generator plugin to merge YAML files seamlessly for real-world use cases.

Merger provides schemaless merge with different merge strategies (StrategicMerge).

• Why
• Features
• Options
• Common use cases
  • 1. Generate multiple manifests from a single base
  • 2. Merge non-manifest files and store them into ConfigMap or Secret
  • 3. Merge lists in manifests without schema or a unique identifier
  • 4. Organize long manifests into smaller ones
• TO-DO
• Project status
• Contributing
• License

Why

The main goal of the Merger plugin is to provide a more flexible way to merge YAML files and extend the strict merge capacities of Kustomize.

Kustomize's default patch strategy for the lists (arrays) is replace, and to change that for the Kubernetes Custom Resource, you must provide the OpenAPI schema of that custom resource, which is only helpful if the lists of that CR have a unique id.

Many people are asking for such functionalities as easy merging CRs, creating a ConfigMap from arbitrary YAML files, and for more details on the challenge of providing OpenAPI schema to merge files, please read the following post: Set OpenAPI patch strategy for Kubernetes Custom Resources.

Features

• Generate multiple resources/manifests from a single base without copying the resources multiple times.
• Merge any manifests (even CustomResources) without needing their OpenAPI schema.
• Merge applications configuration YAML files into a ConfigMap or Secret.
• Merge manifests with a list of maps without a unique identifier (when using x-kubernetes-patch-merge-key is not possible).
• Merge YAML files with different merge strategies (StrategicMerge).

Options

---
apiVersion: generators.kustomize.devopshive.net/v1alpha1
kind: Merger
metadata:
  name: merge
    annotations:
      # Containerized KRM function.
      config.kubernetes.io/function: |
        container:
          image: ghcr.io/devopshivehq/kustomize-generator-merger
          mounts:
          - type: bind
            src: ./
            dst: /mnt
      # Exec KRM functions.
      # config.kubernetes.io/function: |
      #   exec:
      #     path: kustomize-plugin-merger
spec:
  resources:
  - name: example
    input:
      # Available options: overlay,patch.
      # - Overlay: Produce multiple outputs by merging each source with the destination.
      # - Patch: Produce a single output by merging all sources together then with the destination.
      method: overlay
      files:
        # The same as in the KRM container above, omit it if Exec KRM is used.
        root: /mnt
        sources:
        - src01.yaml
        - src02.yaml
        destination: dst.yaml
    merge:
      # Available options: replace,append,combine.
      # - Replace: All keys in source will merge and replace what's in the destination.
      # - Append: Maps from source merged with destination, but the lists will be appended from source to destination.
      # - Combine: Maps from source merged with destination, but the lists will be combined together.
      strategy: combine
    output:
      # Available options: raw,configmap,secret
      format: raw

Common use cases

This section shows a couple of use cases where Merger can help.

1. Generate multiple manifests from a single base

In this case, you have multiple CronJobs, all of which share the same body, but each has a different command or other config.

Read the full example.

2. Merge non-manifest files and store them into ConfigMap or Secret

No plans from Kustomize to support non-manifest files merge and storing them into ConfigMap or Secret. Using Merger you can merge any YAML files like application configuration.

Read the full example.

3. Merge lists in manifests without schema or a unique identifier

Currently, in Kustomize, it's not possible to merge resources without a unique identifier, even with Open API schema.

It's possible to do that using the merge strategy append in Merger (later on, combineWithKey will also be supported).

Read the full example.

4. Organize long manifests into smaller ones

In some use cases (e.g., Crossplane Compositions), you could have a really long YAML manifest, and it's hard to read. You can split that file and use the Merger patch input method to make it a single manifest again.

Read the full example.

TO-DO

• Support combine merge strategy with an identifier key (similar to x-kubernetes-patch-merge-key).
• Configure the output indentation.
• Provide better docs for Merger options.

Project status

Please note that this project is still under development and could have breaking changes, but it will follow the SemVer convention.

Contributing

All feedback and contributions are welcome. If you find any issues or want to contribute, please feel free to fill an issue or create a PR.

License

Merger is an open-source software licensed using the Apache License 2.0. Please see LICENSE for details.