Tellsanguis/Homelab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
25 commits 3 branches 0 tags 227 KiB
Commit graph

25 commits

This branch
This branch
All branches
Author SHA1 Message Date
Tellsanguis
27afd8dad9 feat(cicd): Ajouter gestion automatique des ressources DRBD Linstor
Some checks failed
CD - Deploy Infrastructure / Terraform Validation (push) Successful in 16s
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Failing after 8s
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Failing after 7s
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Failing after 7s
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Has been skipped
Details
CD - Deploy Infrastructure / Deployment Notification (push) Failing after 1s
Details 
- Créer script Python pour gérer les ressources DRBD avant déploiement
  * Vérifie l'existence des ressources Linstor
  * Crée les ressources si nécessaire avec réplication
  * Augmente la taille si elle est insuffisante
  * Noms fixes: pm-a7f3c8e1 (VMID 1000) et pm-b4d2f9a3 (VMID 1001)

- Modifier workflow CI/CD pour intégrer le script Python
  * Ajouter étape de configuration SSH avec secret LINSTOR_SSH_PRIVATE_KEY
  * Exécuter le script avant tofu apply sur pve1 et pve2

- Corriger configuration Terraform des VMs
  * Ajouter vga { type = "std" } pour Standard VGA sur toutes les VMs
  * Ajouter cpu { type = "host" } pour meilleure performance
  * Ajouter replace_triggered_by pour détecter les changements de config
  * Ajouter force_create = true sur pve3 pour gérer VM existante

- Résoudre problèmes identifiés
  * "No Bootable Device" - Résolu avec Standard VGA et CPU host
  * "vmId already in use" - Résolu avec force_create sur etcd-witness
  * Détection des modifications de VM - Résolu avec replace_triggered_by

Documentation SSH créée dans cicd_backup/SETUP_SSH_LINSTOR.md
 2025-11-27 18:06:15 +01:00
Tellsanguis
cc26fb97a6 fix(terraform): Set fixed VMID for VMs to prevent duplication
Some checks failed
CD - Deploy Infrastructure / Terraform Validation (push) Successful in 16s
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Failing after 9s
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Failing after 8s
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Failing after 8s
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Has been skipped
Details
CD - Deploy Infrastructure / Deployment Notification (push) Failing after 1s
Details 
Assign specific VMID to each VM:
- k3s-server-1: 1000
- k3s-server-2: 1001
- etcd-witness: 1002
 2025-11-26 19:41:52 +01:00
Tellsanguis
42be2b3b6b fix(terraform): Configure cluster nodes and storage
Some checks failed
CD - Deploy Infrastructure / Terraform Validation (push) Successful in 17s
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Failing after 1m4s
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Failing after 2m26s
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Failing after 1m47s
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Has been skipped
Details
CD - Deploy Infrastructure / Deployment Notification (push) Failing after 1s
Details
2025-11-26 19:33:19 +01:00
Tellsanguis
5c235e86be feat(terraform): Upgrade to Proxmox provider v3.0.2-rc05 
Update provider version and adjust resource syntax for compatibility.
 2025-11-26 19:31:03 +01:00
Tellsanguis
912e27c30f fix(cd): Add OpenTofu setup step to all deployment jobs
Some checks failed
CD - Deploy Infrastructure / Terraform Validation (push) Successful in 17s
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Failing after 9s
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Failing after 8s
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Failing after 8s
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Has been skipped
Details
CD - Deploy Infrastructure / Deployment Notification (push) Failing after 1s
Details 
Deployment jobs were failing with 'tofu: command not found'. Added Setup OpenTofu step to deploy-pve1, deploy-pve2, and deploy-pve3 jobs.
 2025-11-13 20:03:49 +01:00
Tellsanguis
aaedb0db3a fix(cd): Replace reusable workflow with inline CI jobs
Some checks failed
CD - Deploy Infrastructure / Terraform Validation (push) Successful in 19s
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Failing after 2s
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Failing after 2s
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Failing after 3s
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Has been skipped
Details
CD - Deploy Infrastructure / Deployment Notification (push) Failing after 1s
Details 
Forgejo does not fully support reusable workflows (uses:). Duplicated the Terraform validation job directly in the CD workflow to avoid the blocking state.
 2025-11-13 20:00:53 +01:00
Tellsanguis
f2ed93a018 fix(ci): Add workflow_call trigger to enable CD integration
Some checks are pending
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details 
The CI workflow needs workflow_call to be callable by the CD workflow. Without this, the CD workflow cannot invoke CI as a reusable workflow.
 2025-11-13 19:56:13 +01:00
Tellsanguis
801e130679 fix(ci): Exclude main branch from CI workflow
Some checks are pending
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details 
CI workflow now runs only on feature branches and PRs. On main, only CD workflow runs (which internally calls CI). This prevents duplicate CI runs.
 2025-11-13 19:52:52 +01:00
Tellsanguis
1fc96d7a46 fix(ci): Use environment variables instead of tfvars file
Some checks are pending
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details
CI - Validation / Terraform Validation (push) Successful in 20s
Details
CI - Validation / Ansible Validation (push) Successful in 1m31s
Details
CI - Validation / Kubernetes Validation (push) Successful in 8s
Details
CI - Validation / Security Scan (push) Successful in 21s
Details 
Remove terraform.tfvars.example copy that was overriding secret values. Now using TF_VAR_* environment variables exclusively to properly inject secrets from Forgejo.
 2025-11-13 19:47:47 +01:00
Tellsanguis
bf6be4c637 fix(terraform): Update token ID in example from terraform to opentofu
Some checks failed
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details
CI - Validation / Terraform Validation (push) Successful in 1m6s
Details
CI - Validation / Ansible Validation (push) Has been cancelled
Details
CI - Validation / Kubernetes Validation (push) Has been cancelled
Details
CI - Validation / Security Scan (push) Has been cancelled
Details 
The example file had root@pam!terraform hardcoded, which was overriding the secret value. Updated to match the actual token name.
 2025-11-13 19:45:17 +01:00
Tellsanguis
9103a64669 fix(ci): Rename secrets to avoid FORGEJO_ prefix restriction
Some checks failed
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details
CI - Validation / Terraform Validation (push) Successful in 1m4s
Details
CI - Validation / Ansible Validation (push) Has been cancelled
Details
CI - Validation / Kubernetes Validation (push) Has been cancelled
Details
CI - Validation / Security Scan (push) Has been cancelled
Details 
Forgejo does not allow secret names starting with FORGEJO_. Renamed:
- FORGEJO_TOKEN -> GIT_TOKEN
- FORGEJO_REPO_URL -> GIT_REPO_URL
 2025-11-13 19:41:46 +01:00
Tellsanguis
d940f3a59c fix(ci): Downgrade upload-artifact to v3 for Forgejo compatibility
Some checks are pending
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details
CI - Validation / Terraform Validation (push) Successful in 1m5s
Details
CI - Validation / Ansible Validation (push) Successful in 1m28s
Details
CI - Validation / Kubernetes Validation (push) Successful in 7s
Details
CI - Validation / Security Scan (push) Successful in 17s
Details 
upload-artifact@v4 is not supported on Forgejo/GHES. Downgrade to v3 to ensure artifact uploads work correctly.
 2025-11-13 19:30:40 +01:00
Tellsanguis
739854a371 feat(ci): Update deployment workflow for Ubuntu 24.04 and LINSTOR
Some checks failed
CD - Deploy Infrastructure / ci (push) Waiting to run
Details
CD - Deploy Infrastructure / Deploy on pve1 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve2 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deploy on pve3 (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Validate K3s Cluster (push) Blocked by required conditions
Details
CD - Deploy Infrastructure / Deployment Notification (push) Blocked by required conditions
Details
CI - Validation / Terraform Validation (push) Failing after 1m4s
Details
CI - Validation / Ansible Validation (push) Successful in 1m27s
Details
CI - Validation / Kubernetes Validation (push) Successful in 8s
Details
CI - Validation / Security Scan (push) Successful in 17s
Details 
Update all deployment jobs to use Ubuntu 24.04 LTS template and LINSTOR storage backend for improved reliability.
 2025-11-13 19:06:25 +01:00
Tellsanguis
867c5e6374 feat(terraform): Update to Ubuntu 24.04 LTS and LINSTOR storage
All checks were successful
CI - Validation / Terraform Validation (push) Successful in 17s
Details
CI - Validation / Ansible Validation (push) Successful in 1m31s
Details
CI - Validation / Kubernetes Validation (push) Successful in 8s
Details
CI - Validation / Security Scan (push) Successful in 17s
Details 
Update default configuration to use Ubuntu 24.04 LTS template and configure LINSTOR as the storage backend for improved reliability and performance.
 2025-11-13 18:54:26 +01:00
Tellsanguis
cf5ea11740 fix(flux): Update repository URL from infra to Homelab
All checks were successful
CI - Validation / Terraform Validation (push) Successful in 14s
Details
CI - Validation / Ansible Validation (push) Successful in 55s
Details
CI - Validation / Kubernetes Validation (push) Successful in 7s
Details
CI - Validation / Security Scan (push) Successful in 12s
Details 
- Change GitRepository URL to match new repository name
- Repository renamed from 'infra' to 'Homelab'
 2025-11-11 11:06:16 +01:00
Tellsanguis
78d3a46d31 feat(ci): Add HA support for node failures
Some checks are pending
CI - Validation / Terraform Validation (push) Waiting to run
Details
CI - Validation / Ansible Validation (push) Waiting to run
Details
CI - Validation / Kubernetes Validation (push) Waiting to run
Details
CI - Validation / Security Scan (push) Waiting to run
Details 
Modified CI/CD workflows to gracefully handle Proxmox node failures:

CI Workflow (ci.yml):
- Terraform Plan only runs on main branch (faster CI on feature branches)
- Plan failures on unavailable nodes don't block validation
- Added warning message when plan fails

Deploy Workflow (deploy.yml):
- Added continue-on-error to all deploy jobs (pve1, pve2, pve3)
- Modified cluster validation to require 2/3 nodes (quorum)
- Enhanced deployment summary with success counter
- Exit codes: 0 if >=2 nodes, 1 if 1 node, 1 if 0 nodes

This ensures the infrastructure remains operational even when one
Proxmox node is down, maintaining HA principles.
 2025-11-07 11:32:42 +01:00
Tellsanguis
495bf44ca5 fix(terraform): Add missing VM configurations to tfvars example 
Added VM configuration objects for all three nodes:
- k3s_server_1_config: 6 cores, 12GB RAM, 100G disk
- k3s_server_2_config: 6 cores, 12GB RAM, 100G disk
- etcd_witness_config: 2 cores, 2GB RAM, 20G disk

Removed undeclared 'management_bridge' variable that was causing
warnings in terraform plan.

This allows terraform plan to execute successfully in CI with
the example configuration file.
 2025-11-07 11:24:29 +01:00
Tellsanguis
6178f9f0bc fix(terraform): Update disk syntax for Proxmox provider v2.9 
Changed from nested `disks` block (v3.0 syntax) to flat `disk` block
(v2.9 syntax):
- disks { scsi { scsi0 { disk {...} } } } → disk { slot = 0, ... }
- Added explicit slot, type, and iothread parameters
- Maintains same functionality with v2.9-compatible syntax
 2025-11-07 11:20:07 +01:00
Tellsanguis
a7172070ee fix(terraform): Downgrade Proxmox provider to stable v2.9 
The v3.0 provider is not yet available as a stable release in the
OpenTofu/Terraform registry. Downgraded to v2.9 which is the latest
stable version.

Also fixed minor yamllint issues in flux.yml:
- Added space after comment marker
- Removed trailing blank line
 2025-11-07 10:51:53 +01:00
Tellsanguis
9f2cb11aeb fix(ansible): Resolve YAML linting violations 
Fixed yamllint errors and warnings across all Ansible files:
- Reformatted long lines to stay within 80 character limit
- Standardized boolean values to use true/false instead of yes/no
- Fixed YAML folding syntax for multiline strings
- Removed erroneous triple quotes in k3s-server tasks

This resolves all yamllint issues reported by the CI pipeline.
 2025-11-07 10:40:53 +01:00
Tellsanguis
052006adee feat(ci): Implement multi-module Terraform workflow 2025-11-07 10:27:09 +01:00
Tellsanguis
10ef8a6c1b fix(ci): Address tool findings and workflow errors 2025-11-07 10:21:55 +01:00
Tellsanguis
cb6b1d666b fix(ci): Resolve dependency issues in workflow 2025-11-07 10:13:09 +01:00
Tellsanguis
aa6ac62d92 fix: CI workflow errors (OpenTofu, sudo) 2025-11-07 10:08:20 +01:00
Tellsanguis
850045e7ed feat: Initial commit 2025-11-07 09:33:38 +01:00