added parts

This commit is contained in:
wboughattas
2025-12-30 23:53:49 -05:00
parent 5a12dd0444
commit 786a98f4c5
12 changed files with 1248 additions and 68 deletions

View File

@@ -7,9 +7,7 @@ categories:
highlight: true
---
This blog serves as the public documentation for **Severed**. While the main site provides the high-level vision,
this space is dedicated to the technical source-of-truth for the experiments, infrastructure-as-code, and proprietary
tooling that are used within the cluster.
This blog serves as the public documentation for **Severed**. This space is dedicated to the technical source-of-truth for the experiments, infrastructure-as-code, and proprietary tooling that are used.
### Ecosystem
@@ -23,31 +21,24 @@ The following services are currently active within the `severed.ink` network:
### Core Infrastructure
The ecosystem is powered by a **Home Server Cluster** managed via a **Kubernetes (k3s)** distribution. This setup
prioritizes local sovereignty and GitOps principles.
The ecosystem is powered by a hybrid **Home Server Cluster** managed via a **Kubernetes (k3s)** distribution and AWS services. We prioritize local sovereignty and GitOps principles.
- **CI Pipeline:** Automated build and test suites are orchestrated by a private Jenkins server utilizing self-hosted
runners.
- **CI Pipeline:** Automated build and test suites are orchestrated by a private Jenkins server utilizing self-hosted runners.
- **GitOps & Deployment:** Automated synchronization and state enforcement via **ArgoCD**.
- **Data Layer:** Persistent storage managed by **PostgreSQL**.
- **Telemetry:** Full-stack observability provided by **Prometheus** (metrics) and **Loki** (logs) via **Grafana**.
- **Security Layer:** Push/Pull GitOps operations require an active connection to a **WireGuard (VPN)** for remote
access.
- **Security Layer:** Push/Pull GitOps operations require an active connection to a **WireGuard (VPN)** for remote access.
### Roadmap
Engineering efforts are currently focused on the following milestones:
Efforts are currently focused on the following milestones:
1. **OSS Strategy:** Transitioning from a hybrid of AWS managed services toward a ~100% Open Source Software (OSS) stack.
2. **High Availability (HA):** Implementing a "Cloud RAID-1" failover mechanism. In the event of home cluster
instability, traffic automatically routes to a secondary cloud-instantiated Kubernetes cluster as a temporary
failover.
3. **Data Resilience:** Automating PostgreSQL backup strategies to ensure parity between the primary cluster and the
cloud-based failover.
4. **Storage Infrastructure:** Integrating a dedicated **TrueNAS** node to move from local SATA/NVMe reliance to a
centralized, redundant storage architecture.
2. **High Availability (HA):** Implementing a "Cloud RAID-1" failover mechanism. In the event of home cluster instability, traffic automatically routes to a secondary cloud-instantiated Kubernetes cluster as a temporary failover.
3. **Data Resilience:** Automating PostgreSQL backup strategies to ensure parity between the primary cluster and the cloud-based failover.
4. **Storage Infrastructure:** Integrating a dedicated **TrueNAS** node to move from local SATA/NVMe reliance to a centralized, redundant storage architecture.
### Terminal Redirect
### Redirect
For the full technical portfolio and expertise highlights, visit the main site: