Closed simonhir closed 8 months ago
@simonhir Can u be a bit more specific about the inconsistencies or provide some links.
Currently we're using kustomize. I don't know if helm really helps with that problem without getting too complex
Some example i found just today:
Especially the second example comes up nearly every time i look over some service-configs.
What i think would help with helm or oc process that the config is theoretically static and only the values are changed and set via environment specific configs.
https://git.muenchen.de/digitalisierung/digiwf-ops/-/blob/dev/clusters/k/digiwf-dev/digiwf-engine/service-config.yaml vs https://git.muenchen.de/digitalisierung/digiwf-ops/-/blob/dev/clusters/k/digiwf-processesdemo/digiwf-engine-rest/service-config.yaml (Different Env Values between Envs)
engine != engine-rest
Sorry that is the result when listening to a meeting and looking up something at the same time ...
@zambrovski can you remember the inconsistent file we talked about earlier today? Couldn't find it again. Or was that just between the different branches?
Maybe this is a bigger scope if we consider to move to helm charts
One example i currently struggling with
Hey team! Please add your planning poker estimate with Zenhub @darenegade @lehju @simonhir @StephanStrehlerCGI
The config maps and environment variables are not equal for all digiwf environments. (i.e. not present, other names, ...) This can lead inconsistent misbehavior between different stages.
Probably something like Helm should be used to avoid this in the feature.
Acceptance criteria