further renaming

This commit is contained in:
lukas 2021-07-29 13:25:37 +02:00
parent 3bd2e48408
commit a20c9da0e2
4 changed files with 8 additions and 8 deletions

View file

@ -5,11 +5,11 @@
## Purpose ## Purpose
c4k-mastodon-bot generates a k8s cron-job for your mastodon-bot. All inputs are validated, generaterd yaml will be wellformed, indenet and escaped. c4k-mastodon-bot generates a c4k cron-job for your mastodon-bot. All inputs are validated, generaterd yaml will be wellformed, indenet and escaped.
## Rational ## Rational
There are many comparable solutions for creating k8s deployments like helm or kustomize. Why do we need another one? 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 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. * 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.

View file

@ -38,13 +38,13 @@ wget https://github.com/instrumenta/kubeval/releases/latest/download/kubeval-lin
tar xf kubeval-linux-amd64.tar.gz tar xf kubeval-linux-amd64.tar.gz
sudo cp kubeval /usr/local/bin sudo cp kubeval /usr/local/bin
## remote access to k8s ## remote access to c4k
``` ```
## remote access to k8s ## remote access to c4k
``` ```
scp -r root@devops.test.meissa-gmbh.de:/home/k8s/.kube ~/ scp -r root@devops.test.meissa-gmbh.de:/home/c4k/.kube ~/
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@devops.test.meissa-gmbh.de -L 8002:localhost:8002 -L 6443:192.168.5.1:6443 ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@devops.test.meissa-gmbh.de -L 8002:localhost:8002 -L 6443:192.168.5.1:6443
# add in /etc/hosts "127.0.0.1 kubernetes" # add in /etc/hosts "127.0.0.1 kubernetes"

View file

@ -1,6 +1,6 @@
{ {
"name": "c4k-mastodon-bot", "name": "c4k-mastodon-bot",
"description": "Generate k8s yaml for a mastodon-bot deployment.", "description": "Generate c4k yaml for a mastodon-bot deployment.",
"author": "meissa GmbH", "author": "meissa GmbH",
"version": "0.1.5-SNAPSHOT", "version": "0.1.5-SNAPSHOT",
"homepage": "https://gitlab.com/domaindrivenarchitecture/c4k-mastodon-bot#readme", "homepage": "https://gitlab.com/domaindrivenarchitecture/c4k-mastodon-bot#readme",

View file

@ -65,10 +65,10 @@
<div class="invalid-feedback"><pre id="auth-validation"></pre></div> <div class="invalid-feedback"><pre id="auth-validation"></pre></div>
<br><br> <br><br>
<button type="button" id="generate-button" class="btn btn-primary"> <button type="button" id="generate-button" class="btn btn-primary">
Generate k8s yaml Generate c4k yaml
</button></form><br><br> </button></form><br><br>
<div id="c4k-mastodon-bot-output"> <div id="c4k-mastodon-bot-output">
<label for="output" class="form-label">Your k8s deployment.yaml:</label> <label for="output" class="form-label">Your c4k deployment.yaml:</label>
<textarea name="output" id="output" class="form-control" rows="15"> <textarea name="output" id="output" class="form-control" rows="15">
</textarea> </textarea>
</div> </div>