Kustomize补丁报错：add操作路径缺失，如何修复？

报错信息 #

error: accumulating components: accumulateDirectory:
"recursed accumulation of path
'/runner/_work/ops-infra/ops-infra/current/components/mimir-prod/alertmanager/ops':
add operation does not apply: doc is missing path:
\"/spec/values/alertmanager/fallbackConfig/receivers/-\":
missing value`

现有配置 #

补丁文件（receivers-patch.yaml） #

- op: add
 path: /spec/chart/spec/values/alertmanager/fallbackConfig/receivers/-
  value:
    name: 'slack_receiver'
    slack_configs:
      - channel: "#ops"
        send_resolved: true
        slack_api_url: "https://hooks.slack.com/services/Txxxxx"

Kustomization配置（kustomization.yaml） #

apiVersion: kustomize.config.k8s.io/v1alpha1
kind: Component
patches:
  - path: receivers-patch.yaml
    target:
      kind: HelmRelease
      name: mimir-prod

目标HelmRelease资源 #

apiVersion: helm.toolkit.fluxcd.io/v2beta2
kind: HelmRelease
metadata:
  name: mimir-prod
  namespace: monitoring
spec:
  ...
  values:
    alertmanager:
      fallbackConfig: |
        global:
          pagerduty_url: https://events.pagerduty.com/v2/enqueue
          resolve_timeout: 5m
        receivers:
          - name: 'null'
        route:
          group_by: ['alertname']
          group_interval: 5m
          group_wait: 30s
          receiver: 'null'

错误原因 #

1. 路径错误：补丁里的path写了/spec/chart/spec/values/...，但目标HelmRelease中values直接在spec节点下，正确路径应为/spec/values/alertmanager/fallbackConfig/receivers/-。
2. 核心问题：fallbackConfig是多行字符串（YAML块标量，以|开头），并非结构化的YAML对象。Kustomize的JSON Patch仅能操作结构化的Kubernetes资源字段，无法直接解析和修改字符串内部的YAML内容。

解决方案 #

方案一：将fallbackConfig改为结构化YAML（推荐） #

如果Mimir的Helm Chart支持结构化的fallbackConfig配置（多数现代Chart均支持），先修改原HelmRelease的fallbackConfig，移除|并将内容转为嵌套YAML结构：

spec:
  ...
  values:
    alertmanager:
      fallbackConfig:
        global:
          pagerduty_url: https://events.pagerduty.com/v2/enqueue
          resolve_timeout: 5m
        receivers:
          - name: 'null'
        route:
          group_by: ['alertname']
          group_interval: 5m
          group_wait: 30s
          receiver: 'null'

随后修正补丁文件的路径，调整为正确的JSON Patch：

- op: add
  path: /spec/values/alertmanager/fallbackConfig/receivers/-
  value:
    name: 'slack_receiver'
    slack_configs:
      - channel: "#ops"
        send_resolved: true
        slack_api_url: "https://hooks.slack.com/services/Txxxxx"

方案二：使用字符串替换类补丁（无法修改原结构时） #

若必须保留fallbackConfig为字符串格式，可使用Kustomize的patchStrategicMerge直接替换整个字符串内容。创建如下补丁文件：

apiVersion: helm.toolkit.fluxcd.io/v2beta2
kind: HelmRelease
metadata:
  name: mimir-prod
spec:
  values:
    alertmanager:
      fallbackConfig: |
        global:
          pagerduty_url: https://events.pagerduty.com/v2/enqueue
          resolve_timeout: 5m
        receivers:
          - name: 'null'
          - name: 'slack_receiver'
            slack_configs:
              - channel: "#ops"
                send_resolved: true
                slack_api_url: "https://hooks.slack.com/services/Txxxxx"
        route:
          group_by: ['alertname']
          group_interval: 5m
          group_wait: 30s
          receiver: 'null'

再修改kustomization.yaml引用该补丁：

apiVersion: kustomize.config.k8s.io/v1alpha1
kind: Component
patches:
  - path: receivers-strategic-patch.yaml
    target:
      kind: HelmRelease
      name: mimir-prod

内容的提问来源于stack exchange，提问作者Golide