Parameterize deploy target: build Kind cluster vs app Kind cluster

[jmjava]

Goal

Tekton runs on one Kubernetes API; deploy may target a different Kind cluster (e.g. build/CI on kind-tekton, app on kind-chatbot). Image load and kubectl apply must use the deploy cluster.

Proposed work

• Parameters: Expose target cluster name and/or kubeconfig (Secret) for deploy Tasks (e.g. PipelineRun params: deployContext, deployKubeconfigSecret).
• Kind image load: Document and script kind load docker-image … --name <deploy-cluster> against the app cluster, not the build cluster.
• README / examples: One example PipelineRun showing: build + push (or load) → kubectl --context kind-<app> apply (or kubeconfig from secret).
• Security: If using a kubeconfig Secret, scope RBAC on the target cluster to least privilege for deploy only.

Acceptance criteria

• README explains two-cluster flow and required params/secrets.
• Example works for “Tekton on cluster A, app manifests on cluster B.”

Related

Keeps each app’s Neo4j and workloads on their cluster; build infrastructure stays separate.