**This is an old revision of the document!**
Kustomize explain
``` . ├── base │ ├── app │ │ ├── configmap.yaml │ │ ├── consumer-authproxyworkload.yaml │ │ ├── consumer-deployment.yaml │ │ ├── external-secret-db.yaml │ │ ├── external-secret.yaml │ │ ├── kustomization.yaml │ │ ├── migration-authproxyworkload.yaml │ │ ├── migration-deployment.yaml │ │ ├── rest-authproxyworkload.yaml │ │ ├── rest-deployment.yaml │ │ ├── rest-scaled-object.yaml │ │ ├── rest-service.yaml │ │ ├── service-account.yaml │ │ └── virtual-service.yaml │ └── infra │ ├── postgres │ │ ├── external-secret.yaml │ │ └── kustomization.yaml │ └── redis │ ├── external-secret.yaml │ └── kustomization.yaml ├── envs │ └── dev │ ├── app │ │ ├── configmap.yaml │ │ ├── consumer-deployment.yaml │ │ ├── consumer-resources.yaml │ │ ├── kustomization.yaml │ │ ├── migration-deployment.yaml │ │ ├── migration-resources.yaml │ │ ├── rest-deployment.yaml │ │ ├── rest-resources.yaml │ │ ├── service-account.yaml │ │ └── virtual-service.yaml │ └── infra │ ├── postgres │ │ └── kustomization.yaml │ └── redis │ └── kustomization.yaml `` `
Inheritance
How Kafka Topics Actually Get Included
The Kafka topic fields come from the base ConfigMap through Kustomize's inheritance mechanism. Here's the process:
- Base ConfigMap defines the Kafka topic fields with ENV_PLACEHOLDER values
- Production ConfigMap completely replaces the base ConfigMap BUT only defines the fields it explicitly contains
- Replacements then modify the KAFKA_* fields that were inherited from the base
