homelab

riotpiao-poimen/homelab

Fork 0

Author	SHA1	Message	Date
rock	95738b71bf	fix: vendor Tekton release.yaml for proper ArgoCD management ROOT CAUSE: - tektoncd/pipeline config/ dir uses ko:// image refs (build-time placeholders) - ArgoCD synced the raw dev manifests → InvalidImageName on all pods - tektoncd/operator requires its own CRDs and controller (too heavy) - Tekton has no official Helm chart FIX: - Vendor the pre-built release.yaml (v0.68.0) into k8s/infra/tekton/ - Point ArgoCD Application at our own repo (forgejo) - Release contains real container images (ghcr.io/tektoncd/pipeline/*) - Remove external tektoncd repo from AppProject (not needed) TO UPGRADE TEKTON: 1. Download new release from github.com/tektoncd/pipeline/releases 2. Replace k8s/infra/tekton/release.yaml 3. Commit — ArgoCD syncs automatically	2026-09-13 15:05:26 +09:00
rock	1d6b9b5013	fix: use tektoncd/operator for proper K8s-native Tekton installation ROOT CAUSE: - Previous Application pointed to storage bucket (not valid ArgoCD source) - ArgoCD couldn't sync manifests from non-git/non-helm source - tektoncd/operator is the official way to install Tekton SOLUTION: - Switch to tektoncd/operator repository - Use operator's config/install path (contains release manifests) - Proper GitOps flow: ArgoCD watches operator repo → syncs manifests → K8s reconciles BENEFITS: ✓ Official Tekton approach ✓ Proper K8s Operator pattern ✓ ArgoCD-compatible (git source) ✓ Automatic updates from upstream ✓ Full GitOps workflow	2026-09-13 14:51:54 +09:00
rock	28a9ef88a0	feat: add Tekton Pipelines for CI/CD orchestration Install Tekton Pipelines via ArgoCD for Kubernetes-native CI/CD: COMPONENTS: - Tekton Pipelines: CNCF-standard test orchestration - Task/Pipeline CRDs: Reusable workflow definitions - PipelineRun: Ephemeral execution instances - ArgoCD Application: GitOps-managed installation INTEGRATION: - homelab-frontend CI triggers PipelineRun via Kubernetes API - Tests run in cluster against actual services - Results flow back to CI for pass/fail decisions - Image promotion only on test success FILES: - k8s/infra/tekton/: Tekton infrastructure setup - namespace.yaml: tekton-pipelines namespace - kustomization.yaml: Release manifest reference - k8s/argocd/apps/06-ci-cd.yaml: ArgoCD Application - k8s/argocd/projects/homelab-project.yaml: Added Tekton repos WAVE ORDERING: Wave 06 (CI/CD) is deployed after: - Wave 05 (Networking) - Wave 04 (Core components) But before Wave 40+ (Applications) BENEFITS: ✓ Kubernetes-native (no external CI runners) ✓ GitOps-managed (everything in git via ArgoCD) ✓ CNCF-standard (industry-proven Tekton project) ✓ Pre-merge testing (tests must pass before deploy) ✓ Observable (logs, status, results tracking) ✓ Secure (non-root, resource limits, RBAC)	2026-09-13 14:46:00 +09:00

Author

SHA1

Message

Date

rock

95738b71bf

fix: vendor Tekton release.yaml for proper ArgoCD management

ROOT CAUSE:
- tektoncd/pipeline config/ dir uses ko:// image refs (build-time placeholders)
- ArgoCD synced the raw dev manifests → InvalidImageName on all pods
- tektoncd/operator requires its own CRDs and controller (too heavy)
- Tekton has no official Helm chart

FIX:
- Vendor the pre-built release.yaml (v0.68.0) into k8s/infra/tekton/
- Point ArgoCD Application at our own repo (forgejo)
- Release contains real container images (ghcr.io/tektoncd/pipeline/*)
- Remove external tektoncd repo from AppProject (not needed)

TO UPGRADE TEKTON:
  1. Download new release from github.com/tektoncd/pipeline/releases
  2. Replace k8s/infra/tekton/release.yaml
  3. Commit — ArgoCD syncs automatically

2026-09-13 15:05:26 +09:00

rock

1d6b9b5013

fix: use tektoncd/operator for proper K8s-native Tekton installation

ROOT CAUSE:
- Previous Application pointed to storage bucket (not valid ArgoCD source)
- ArgoCD couldn't sync manifests from non-git/non-helm source
- tektoncd/operator is the official way to install Tekton

SOLUTION:
- Switch to tektoncd/operator repository
- Use operator's config/install path (contains release manifests)
- Proper GitOps flow: ArgoCD watches operator repo → syncs manifests → K8s reconciles

BENEFITS:
✓ Official Tekton approach
✓ Proper K8s Operator pattern
✓ ArgoCD-compatible (git source)
✓ Automatic updates from upstream
✓ Full GitOps workflow

2026-09-13 14:51:54 +09:00

rock

28a9ef88a0

feat: add Tekton Pipelines for CI/CD orchestration

Install Tekton Pipelines via ArgoCD for Kubernetes-native CI/CD:

COMPONENTS:
- Tekton Pipelines: CNCF-standard test orchestration
- Task/Pipeline CRDs: Reusable workflow definitions
- PipelineRun: Ephemeral execution instances
- ArgoCD Application: GitOps-managed installation

INTEGRATION:
- homelab-frontend CI triggers PipelineRun via Kubernetes API
- Tests run in cluster against actual services
- Results flow back to CI for pass/fail decisions
- Image promotion only on test success

FILES:
- k8s/infra/tekton/: Tekton infrastructure setup
  - namespace.yaml: tekton-pipelines namespace
  - kustomization.yaml: Release manifest reference
- k8s/argocd/apps/06-ci-cd.yaml: ArgoCD Application
- k8s/argocd/projects/homelab-project.yaml: Added Tekton repos

WAVE ORDERING:
Wave 06 (CI/CD) is deployed after:
  - Wave 05 (Networking)
  - Wave 04 (Core components)
But before Wave 40+ (Applications)

BENEFITS:
✓ Kubernetes-native (no external CI runners)
✓ GitOps-managed (everything in git via ArgoCD)
✓ CNCF-standard (industry-proven Tekton project)
✓ Pre-merge testing (tests must pass before deploy)
✓ Observable (logs, status, results tracking)
✓ Secure (non-root, resource limits, RBAC)

2026-09-13 14:46:00 +09:00

Compare commits

Diff Content Not Available