There are many comparable solutions for creating c4k deployments like helm or kustomize. Why do we need another one?
* We like the simplicity of kustomize. Yaml in, yaml out, the ability to lint the result and the option to split large yaml files into objects. But a simple overwriting per environment may not be enough ...
@ -21,24 +21,26 @@ Our convention 4 kubernetes c4k-* tools combine the advantages of both approache
## Usage
c4k-common provides the basic functionality for our c4k-modules.
## Refactoring & Module Overview
| Module | Version | common postgres | frontend script | [backup as deployment][bak1] | [use common pred. ][com1] | [configs as EDN and YAML][yaml1] | [renamed test-helper][th1] |