softplayer
/
softplayer-ansible
5
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases Activity
14 Commits 1 Branch 0 Tags 68 KiB
Makefile 66.6%
Jinja 23.2%
Dockerfile 10.2%
Go to file
Nikolai Rodionov 6b66d8cc25
ci/woodpecker/push/build Pipeline was successful Details
Disable serbicelb 		2024-04-26 16:05:34 +02:00
.woodpecker Run with seccontext priv 2024-04-01 14:46:26 +02:00
bin Init commit 2024-03-28 18:29:07 +01:00
group_vars Init commit 2024-03-28 18:29:07 +01:00
playbooks Disable serbicelb 2024-04-26 16:05:34 +02:00
resources Init commit 2024-03-28 18:29:07 +01:00
.containerignore Init commit 2024-03-28 18:29:07 +01:00
.gitignore Init commit 2024-03-28 18:29:07 +01:00
.sops.yaml Init commit 2024-03-28 18:29:07 +01:00
Containerfile Install reqs to the final container 2024-04-02 14:12:22 +02:00
LICENSE Initial commit 2024-03-10 14:46:27 +00:00
Makefile Init commit 2024-03-28 18:29:07 +01:00
README.md Init commit 2024-03-28 18:29:07 +01:00
requirements.txt Init commit 2024-03-28 18:29:07 +01:00
requirements.yml Fix k3s collection installation 2024-04-02 13:13:13 +02:00

README.md

softplayer-ansible

Hetzner

There must be 3 kinds of playbooks: - Bootstrap - Maintenance - Cleanup

Bootstrap playbooks should only be executed when a new environment is created, for example, it should

  1. Prepare the cloud infrastructure
  2. Install setup nodes
  3. Bootstrap a k3s cluster
  4. Create an admin k8s config

Cleanup should simply remove the whole cloud infrastructure