Targeting the base of an overlay set #5513

randeepbydesign · 2025-09-11T14:25:17Z

randeepbydesign
Sep 11, 2025

I have a service dummy-service that deploys via a helmchart.

Based on traffic pattern, I need to deploy the same image as a different service with a different configuration. So I create a dummy-service-rock service with a similar setup:

# base/cluster/_base/helmrelease.yaml
---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: dummy-service
  namespace: ktst
spec:
  values:
    env:
      - name: AAA
        value: 'Hello'
    name: ktst-dummy-service
    bootstrap:
      spring:
        profiles:
          include:
            - main

# base/cluster/_base/kustomization.yaml
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ktst
resources:
  - helmrelease.yaml

# base/cluster/main/kustomization.yaml
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ktst
resources:
  - ../_base

The definition for my replica rock service:

# base/cluster/rock/kustomization.yaml
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ktst
nameSuffix: -rock
resources:
  - ../_base
patches:
  - target:
      name: dummy-service
    patch: |-
      - op: add
        path: /spec/values/name
        value: ktst-dummy-service-rock
      - op: add
        path: /spec/values/bootstrap/spring/profiles/include
        value:
          - rock

and I make all services referential from an env kustomization:

# base/env/kustomization.yaml
# set this up as a way to reference everything in _base
--- 

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ktst
resources:
  - ../cluster/main
  - ../cluster/rock

Now let's say I want to modify the base service only in the dev env.

For the purpose of this example, let's say when I deploy to the dev env I want to add an env variable to the list of vars available:

---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ktst
resources:
  - ../base/env
patches:
  - patch: |-
      - op: add
        path: /spec/values/env/-
        value:
          name: BBB
          value: 'World'
    target:
      name: ^dummy-service$

The problem is... no matter what value I use for target, it modifies both dummy-service and dummy-service-rock.

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: dummy-service
  namespace: ktst
spec:
  values:
    bootstrap:
      spring:
        profiles:
          include:
          - main
    env:
    - name: AAA
      value: Hello
    - name: BBB
      value: World
    name: ktst-dummy-service
---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: dummy-service-rock
  namespace: ktst
spec:
  values:
    bootstrap:
      spring:
        profiles:
          include:
          - rock
    env:
    - name: AAA
      value: Hello
    - name: BBB
      value: World
    name: ktst-dummy-service-rock

I've tried the following permutations for target.name:

dummy-service
^dummy-service$
".+service$"
But all of them modify both main and rock configurations. On the other hand, if I target rock only with:

.+-rock$
dummy-service-rock
^dummy-service-rock$
it modifies rock and leaves main alone. Can someone point me in the right direction here? Thanks!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Targeting the base of an overlay set #5513

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Targeting the base of an overlay set #5513

Uh oh!

randeepbydesign Sep 11, 2025

Replies: 0 comments

randeepbydesign
Sep 11, 2025