No description

Find a file

jerger 4cfe791e85 Breaking-Change: generate-pvc now needs a config. introduced storage-size & storage-class-name		2022-02-12 18:28:35 +01:00
doc	pin postgres to version 13	2021-10-08 11:41:46 +02:00
src	Breaking-Change: generate-pvc now needs a config.	2022-02-12 18:28:35 +01:00
.gitignore	refactor common parts	2021-06-18 15:49:43 +02:00
.gitlab-ci.yml	tags are not on a branche!	2021-07-09 19:58:42 +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	Breaking-Change: generate-pvc now needs a config.	2022-02-12 18:28:35 +01:00
project.clj	Breaking-Change: generate-pvc now needs a config.	2022-02-12 18:28:35 +01:00
README.md	added new refactoring	2021-11-12 11:15:59 +01:00
shadow-cljs.edn	moved hickory framework to commons	2021-09-03 12:59:28 +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:

Module	Version	common postgres	frontend script	backup as deployment	speced c4k-common
c4k-mastodon-bot	0.1	-
c4k-keycloak	0.2
c4k-jira	1.0	x	x	x
c4k-nextcloud	1.0	x	x	x	x