e78000831e
Hearth is the infrastructure home for the letemcook ecosystem. Ported from coherence-mcp/infra: - Terraform modules (VPC, EKS, IAM, NLB, S3, storage) - Kubernetes manifests (Forgejo, ingress, cert-manager, karpenter) - Deployment scripts (phased rollout) Status: Not deployed. EKS cluster needs to be provisioned. Next steps: 1. Bootstrap terraform backend 2. Deploy phase 1 (foundation) 3. Deploy phase 2 (core services including Forgejo) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
37 lines
946 B
YAML
37 lines
946 B
YAML
# Forgejo Persistent Volume Claim
|
|
# RFC 0040: Self-Hosted Core Services
|
|
#
|
|
# NOTE: For HA setup with multiple replicas, consider:
|
|
# 1. Using EFS (AWS) or similar shared filesystem for /data/git
|
|
# 2. Using S3 for LFS storage
|
|
# 3. This PVC works for single-replica or ReadWriteMany storage classes
|
|
apiVersion: v1
|
|
kind: PersistentVolumeClaim
|
|
metadata:
|
|
name: forgejo-data
|
|
namespace: forgejo
|
|
labels:
|
|
app.kubernetes.io/name: forgejo
|
|
app.kubernetes.io/part-of: core-services
|
|
spec:
|
|
accessModes:
|
|
- ReadWriteMany
|
|
storageClassName: efs-sc
|
|
resources:
|
|
requests:
|
|
storage: 100Gi
|
|
---
|
|
# Alternative: Use GP3 with single replica
|
|
# Uncomment this and comment above for single-replica setup
|
|
# apiVersion: v1
|
|
# kind: PersistentVolumeClaim
|
|
# metadata:
|
|
# name: forgejo-data
|
|
# namespace: forgejo
|
|
# spec:
|
|
# accessModes:
|
|
# - ReadWriteOnce
|
|
# storageClassName: gp3-encrypted
|
|
# resources:
|
|
# requests:
|
|
# storage: 100Gi
|