ansible v2

Author: NadeeshaNJ

ansible/vars/main.yml

@@ -1,5 +1,5 @@
 ---
 github_username: "x-access-token"
-github_pat: "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"
+github_pat: "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"
 git_repo_url: "https://github.com/Healthcare-Monitoring-System/d2-data-intelligence.git"
 repo_dest: "/opt/d2-data-intelligence"

ansible_use.md

@@ -0,0 +1,64 @@
+# D2 Ansible Deployment Guide
+
+This guide explains how to use the Ansible playbook to fully automate the deployment of the D2 Data Intelligence stack to a fresh EC2 instance.
+
+## Prerequisites
+
+1. **Local SSH Setup**: Ensure your `~/.ssh/config` is set up with an alias for your EC2 instance (e.g., `king`), or know the IP and path to your private key (e.g., `Nadeesha.pem`).
+2. **GitHub PAT**: The repository (`d2-data-intelligence`) is private. We use a GitHub Personal Access Token (PAT) so Ansible and ArgoCD can automatically fetch the repository.
+
+### Generating a GitHub PAT
+1. Go to your GitHub account **Settings** -> **Developer Settings** -> **Personal Access Tokens** -> **Tokens (classic)**.
+2. Click **Generate new token (classic)**.
+3. Name it (e.g., `d2-deployment`), set the expiration, and check the **`repo`** scope box.
+4. Generate the token and copy it (it starts with `ghp_` or `github_pat_`).
+
+## Configuration
+
+1. **Inventory (`inventory.ini`)**:
+   Ensure `inventory.ini` points to your instance. If using your SSH config alias `king`, simply use:
+   ```ini
+   [d2_servers]
+   king ansible_host=<IP> ansible_user=ubuntu ansible_ssh_private_key_file=~/.ssh/Nadeesha.pem
+   ```
+
+2. **Variables (`vars/main.yml`)**:
+   Paste your GitHub PAT into `vars/main.yml`:
+   ```yaml
+   github_username: "x-access-token"
+   github_pat: "github_pat_YOUR_TOKEN_HERE"
+   ```
+   *(Note: The username can safely be `x-access-token`. GitHub only cares about the valid token).*
+
+## Running the Playbook
+
+To provision a fresh server, run the following from your laptop:
+
+```bash
+cd ansible
+ansible-playbook site.yml
+```
+
+### What the Playbook Does:
+- Upgrades system packages and configures the `ufw` firewall (opening ports 80, 443, 6443, 5432, 8086, etc.).
+- Installs K3s (Kubernetes) automatically.
+- Installs ArgoCD natively using Kubernetes Server-Side Apply to bypass manifest size limits.
+- Clones the private repository to the server using your PAT.
+- Injects your PAT into ArgoCD as a Kubernetes Secret so it can sync manifests from GitHub continuously.
+- Deploys all ArgoCD applications into the cluster.
+
+## Post-Deployment & Troubleshooting
+
+**Checking the cluster:**
+SSH into the server:
+```bash
+ssh king
+```
+Check the pods:
+```bash
+kubectl get pods -n d2 -o wide
+```
+*Note: Do **NOT** use `sudo kubectl`. The `ubuntu` user has been explicitly configured to communicate with K3s. Using `sudo` will cause it to fail looking for root credentials.*
+
+**Checking ArgoCD:**
+The playbook automatically prints the initial ArgoCD admin password at the end of the run. You can use it to log into the UI (once exposed) or via the CLI.