No description

Find a file

erik 1cadd0e993 [WIP] Update postgres and tests		2022-11-08 13:37:08 +01:00
doc	refactor	2022-09-02 11:10:23 +02:00
src	[WIP] Update postgres and tests	2022-11-08 13:37:08 +01:00
.gitignore	Add ingress definitions to c4k-common	2022-10-19 09:25:37 +02:00
.gitlab-ci.yml	Update CI to show failing tests	2022-09-02 10:13:52 +02:00
LICENSE	changed license	2021-06-18 15:36:16 +02:00
package.json	yaml multimethod, added postgres	2021-07-09 16:53:38 +02:00
project-cljs.clj	version bump	2022-08-05 08:54:11 +02:00
project.clj	version bump	2022-08-05 08:54:11 +02:00
README.md	update refactoring state	2022-07-29 14:19:05 +02:00
shadow-cljs.edn	Update CI to show failing tests	2022-09-02 10:13:52 +02:00

convention 4 kubernetes: c4k-common

Purpose

c4k-common ....

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 ...
We like helm packages. A package encapsulates the setup for an application. On the one hand, but on the other hand we don't like the idea of having to program and debug in a template language. We can program much better in real programming languages.

Our convention 4 kubernetes c4k-* tools combine the advantages of both approaches: