softplayer
/
softplayer-ansible
5
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases Activity
25 Commits 1 Branch 0 Tags 88 KiB
Makefile 65.3%
Jinja 24%
Dockerfile 10.7%
Go to file
Nikolai Rodionov 9d73894ae3
ci/woodpecker/push/build Pipeline was successful Details
Prefire A name 		2024-05-09 12:43:40 +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 Add cloudflare support' 2024-05-03 18:34:26 +02:00
playbooks Prefire A name 2024-05-09 12:43:40 +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 Add yq to the image 2024-05-07 14:16:57 +02:00
LICENSE Initial commit 2024-03-10 14:46:27 +00:00
Makefile Add cloudflare support' 2024-05-03 18:34:26 +02: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