No description
| doc | ||
| image | ||
| public | ||
| src | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| LICENSE | ||
| package.json | ||
| project.clj | ||
| README.md | ||
| shadow-cljs.edn | ||
| valid-auth.edn | ||
| valid-config.edn | ||
convention 4 kubernetes: c4k-keycloak
chat over e-mail | 
team@social.meissa-gmbh.de | Website & Blog
Purpose
c4k-keycloak ....
Rational
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:
- Packages for one application
- Programming in clojure
- yaml / edn as input and output, no more magic
- good validation, integration as api, cli or in the browser
Try out
Click on the image to try out live in your browser:
Your input will stay in your browser. No server interaction is required.
You will also be able to try out on cli:
target/graalvm/c4k-keycloak src/test/resources/valid-config.edn src/test/resources/valid-auth.edn | kubeval -
target/graalvm/c4k-keycloak src/test/resources/valid-config.edn src/test/resources/valid-auth.edn | kubectl apply -f -
License
Copyright © 2021 meissa GmbH Licensed under the Apache License, Version 2.0 (the "License") Pls. find licenses of our subcomponents here
