feat/tekton-pipelines-ci
main
Install Tekton Pipelines (CNCF CI/CD) via ArgoCD for pre-merge integration testing.
Adds Tekton Pipelines to the homelab cluster infrastructure for orchestrating CI/CD workflows:
Tekton Pipelines Installation
ArgoCD Management
Integration with homelab-frontend
Cluster Infrastructure (homelab): └── Tekton Pipelines (Wave 06 - CI/CD) ├── Task: Run integration tests ├── Pipeline: Orchestrate workflows └── PipelineRun: Execute on demand Application: homelab-frontend └── CI Workflow (.gitea/workflows/ci.yaml) ├── Build image ├── Create PipelineRun ├── Wait for completion └── Promote to :latest (if pass)
k8s/infra/tekton/namespace.yaml
k8s/infra/tekton/kustomization.yaml
k8s/argocd/apps/06-ci-cd.yaml
k8s/argocd/projects/homelab-project.yaml
Wave 06 (CI/CD) is deployed in proper order:
✓ Kubernetes-Native: Uses standard K8s CRDs (Task, Pipeline, PipelineRun) ✓ GitOps: Everything in git, managed by ArgoCD, no manual kubectl ✓ Pre-Merge Testing: Tests must pass before code deploys ✓ Observable: Logs, status, results tracking ✓ Secure: Non-root containers, resource limits, RBAC ✓ CNCF-Standard: Industry-proven Tekton project ✓ Scalable: Can add more tests/tasks without complexity
This homelab PR works with homelab-frontend PR #25:
Together they form complete GitOps CI/CD pipeline.
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)
No dependencies set.
The note is not visible to the blocked user.
Install Tekton Pipelines (CNCF CI/CD) via ArgoCD for pre-merge integration testing.
What This Does
Adds Tekton Pipelines to the homelab cluster infrastructure for orchestrating CI/CD workflows:
Tekton Pipelines Installation
ArgoCD Management
Integration with homelab-frontend
Architecture
Files Added
k8s/infra/tekton/namespace.yaml- Tekton namespacek8s/infra/tekton/kustomization.yaml- Release manifest referencek8s/argocd/apps/06-ci-cd.yaml- ArgoCD Application (Wave 06)k8s/argocd/projects/homelab-project.yaml- Added Tekton reposWave Ordering
Wave 06 (CI/CD) is deployed in proper order:
Benefits
✓ Kubernetes-Native: Uses standard K8s CRDs (Task, Pipeline, PipelineRun)
✓ GitOps: Everything in git, managed by ArgoCD, no manual kubectl
✓ Pre-Merge Testing: Tests must pass before code deploys
✓ Observable: Logs, status, results tracking
✓ Secure: Non-root containers, resource limits, RBAC
✓ CNCF-Standard: Industry-proven Tekton project
✓ Scalable: Can add more tests/tasks without complexity
Integration with PR #25
This homelab PR works with homelab-frontend PR #25:
Together they form complete GitOps CI/CD pipeline.
Testing After Merge
Review Checklist