// Use when setting up or tearing down a local kind cluster for running Tekton task tests
Use when confused by CI behavior, investigating why tests did or did not run, or troubleshooting GitHub Actions workflows
Use when a Tekton task test fails in CI or locally and you need to find the root cause
Use when preparing, reviewing, or finalizing a pull request to this Tekton catalog repository
Use when running, writing, or troubleshooting functional tests for Tekton tasks in this catalog
| name | setting-up-kind-cluster |
| description | Use when setting up or tearing down a local kind cluster for running Tekton task tests |
Task tests require a kind cluster with Konflux CI installed. This skill covers setup, teardown, and common issues.
git clone https://github.com/konflux-ci/konflux-ci.git /tmp/konflux-ci
kind create cluster --config /tmp/konflux-ci/kind-config.yaml
cd /tmp/konflux-ci
./deploy-deps.sh
./wait-for-all.sh
./deploy-konflux.sh
./deploy-test-resources.sh
kubectl get pods -A | grep -v Running | grep -v Completed
All pods should be Running or Completed. If not, wait and re-check.
Ensure these are on PATH: tkn, kubectl, yq, jq
# tkn (Tekton CLI)
# See https://tekton.dev/docs/cli/ or use the repo's custom action logic:
# .github/actions/install-tkn/
kind delete cluster
To clean up a specific test namespace without destroying the cluster:
kubectl delete namespace <task-name>-<version-hyphens>
konflux-ci commit (ab849590); for local dev, using main is fine but results may differdeploy-deps.sh hangs, check kubectl get events -A for image pull or resource issueskonflux-ci/kind-config.yaml sets up port mappings and extra mounts — don't use a bare kind create clusterAfter setup, verify Tekton is working:
kubectl get pods -n tekton-pipelines
tkn version