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
This commit is contained in:
@@ -11,9 +11,13 @@ spec:
|
||||
project: homelab
|
||||
|
||||
source:
|
||||
repoURL: https://github.com/tektoncd/pipeline.git
|
||||
# tektoncd/operator is the official Kubernetes Operator for Tekton
|
||||
# It manages the lifecycle of Tekton Pipelines installation
|
||||
# Source: https://github.com/tektoncd/operator
|
||||
repoURL: https://github.com/tektoncd/operator.git
|
||||
targetRevision: main
|
||||
path: config/release
|
||||
# The operator's config directory contains the latest release manifests
|
||||
path: config/install
|
||||
|
||||
destination:
|
||||
server: https://kubernetes.default.svc
|
||||
|
||||
Reference in New Issue
Block a user