You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

bom d635988f5a Remove router.tls annotation This specialized the ingress for https connections which is no longer the case for the combined ingress		2 years ago
doc	refactor	2 years ago
src	Remove router.tls annotation	2 years ago
.gitignore	add .clj-kondo and .lsp	2 years ago
.gitlab-ci.yml	Update CI to show failing tests	2 years ago
LICENSE	changed license	3 years ago
README.md	Update Refactorings	2 years ago
package.json	Fix test and update deps	2 years ago
project-cljs.clj	version bump	2 years ago
project.clj	version bump	2 years ago
shadow-cljs.edn	Update CI to show failing tests	2 years ago

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:

c4k-common provides the basic functionality for our c4k-modules.

Module	Version	common postgres	frontend script	backup as deployment	use common pred.	configs as EDN and YAML	renamed test-helper	common load-as-edn
c4k-mastodon-bot	0.1	-
c4k-keycloak	0.2
c4k-jira	1.1	x	x	x
c4k-nextcloud	2.0	x	x	x	x	x
c4k-jitsi	1.2
c4k-gittea	1.0	x	x	x	x	x	x
c4k-shynet	1.0
c4k-website	0.1	x	x	x	x	x	x	x