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:
2026-09-13 15:10:39 +09:00
parent 5f16d5c6a3
commit b06ee310b5
6 changed files with 330 additions and 32 deletions
+2 -2
View File
@@ -45,8 +45,8 @@ spec:
- https://stakater.github.io/stakater-charts
# ArgoCD ecosystem charts
- https://argoproj.github.io/argo-helm
# Tekton Pipelines (CNCF CI/CD)
- https://github.com/tektoncd/pipeline.git
# Tekton Pipelines (CNCF CI/CD) — uses tektoncd/operator
- https://github.com/tektoncd/operator.git
destinations:
- server: https://kubernetes.default.svc
namespace: "*"