Re-add previous ansible roles

Co-authored-by: Hassan Abouelela <[email protected]>
Co-authored-by: Johannes Christ <[email protected]>
Co-authored-by: Joe Banks <[email protected]>
Co-authored-by:  MarkKoz <[email protected]>

1 files changed, 0 insertions, 34 deletions

diff --git a/inventory/README.md b/inventory/README.md
deleted file mode 100644
index 294d80b..0000000
--- a/inventory/README.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Inventory
-The main inventory for the pydis cluster.
-
-## Content
-This directory is not covered by ansible-lint, and should generally not be used to add new configuration.
-Instead, that should be placed appropriately within the project as normal.
-- `hosts.yaml`: The main hosts file for our infrastructure.
-
-## Deployment
-To deploy the kuberspray roles on our infrastructure, run the following commands in the root directory.
-
-### Environment
-Run the following commands, then enter your sudo password in the file that opens:
-
-```shell
-python3.10 -m venv venv
-source venv/bin/activate
-pip install -r kubespray/requirements-2.12.txt
-export ANSIBLE_CONFIG=ansible.cfg
-```
-
-### Deployment
-Enter your username into the command below, and run (this will take a while, so go grab a drink):
-
-```
-ansible-playbook kubespray/cluster.yml -v -u <user>
-```
-
-One useful argument for the command above is `--become-password-file`
-which should point to a file with your sudo password for seamless execution.
-
-Additionally, you may find it helpful to pre-configure all hosts in known_hosts
-to prevent the prompt from timing out during execution. This can be achieved by SSHing
-into the machines beforehand, or running an ad-hoc command and confirming all hosts.