properly reflect the changes required by the argo applicationSet

This commit is contained in:
2025-10-14 12:27:03 +02:00
parent 6a5c203f76
commit 751caf4233
11 changed files with 44 additions and 130 deletions

View File

@@ -22,7 +22,7 @@ spec:
- containerPort: 8000
env:
- name: MEMCACHED_HOST_PATH
value: "memcached:11211"
value: "memcached" # this value may be changed by kustomize nameReference transformer
- name: NUM_WORKERS
value: "3"
- name: OSM_CACHE_DIR
@@ -44,4 +44,3 @@ spec:
persistentVolumeClaim:
claimName: osm-cache

View File

@@ -8,3 +8,7 @@ resources:
- service.yaml
- ingress.yaml
- memcached/
configurations:
# allow nameReference to work with different mentions of the same resource as well
- name_reference.yaml

13
base/name_reference.yaml Normal file
View File

@@ -0,0 +1,13 @@
nameReference:
# Tie target Service metadata.name to IngressRoute's spec.routes.services.name
# Once Service name is changed, the IngressRoute referrerd service name will be changed as well.
- kind: Service
fieldSpecs:
- kind: IngressRoute
path: spec/routes/services/name
# same for the memcached service: since separate overlays may change its name the env variable in the deployment should be updated accordingly
- kind: Service
fieldSpecs:
- kind: Deployment
path: spec/template/spec/containers/env/value