How tektoncd/dashboard works
Project type and purpose
• This is a full-stack web application (“Tekton Dashboard”) consisting of:
– A Go‐based backend (cmd/dashboard, pkg/) that exposes REST endpoints and serves static assets
– A React/Vite single-page frontend (src/, packages/components, packages/graph, packages/utils)
– Kubernetes/Tekton deployment manifests (config/, tekton/) for running on a cluster
• Purpose: provide a web UI for viewing and managing Tekton Pipelines and Triggers via the Kubernetes API
Key architectural components
– Frontend SPA
• src/containers, src/components: container & presentational components
• packages/components, packages/graph, packages/utils: shared component libraries and graph rendering
• Storybook & Cypress (packages/e2e) for component and E2E testing
• Vite-based build (vite.config.js)
– Backend API server
• cmd/dashboard/main.go: entrypoint
• pkg/router/router.go: HTTP routing
• pkg/endpoints/*.go: REST handlers for pipelines, tasks, logs, health, etc.
• pkg/utils (csrf, proxy): cross-site protection, proxying to k8s API
• No external database: state is fetched directly from Kubernetes API
– Kubernetes integration
• config/: kustomize overlays for namespace, roles, deployments, services
• tekton/: Tekton pipeline definitions for CI/CD (build, publish, release pipelines)
– CI/CD pipelines
• GitHub Actions (.github/workflows) and Tekton pipelines (tekton/) for build/test/release
– External systems
• Kubernetes API server (CRDs: PipelineRun, TaskRun, Triggers, etc.)
• Git repositories (import resources)
• OAuth2 proxy if enabled (docs/walkthrough)
How to represent this
• Browser (React SPA)
• Frontend static files (served by Go server)
• Backend API server (Go)
• Kubernetes API server (with Tekton CRDs)
• CI/CD pipelines (GitHub Actions, Tekton pipelines)
• External Git server (for resource import)
• (Optional) OAuth2 Proxy / Identity Provider
1. User → Browser (interacts via UI)
2. Browser → Backend API (HTTPS calls to REST endpoints)
3. Backend → Kubernetes API (client-go requests for CRDs)
4. Backend → External Git (import endpoints)
5. GitHub Actions / Tekton pipelines → Build & deploy steps → Kubernetes cluster
6. Browser ←> OAuth2 Proxy (if authentication is enabled)
c. Architectural patterns & design principles:
• SPA with container/presentational component separation
• Backend API follows REST principles, no DB – acting as a proxy to k8s API
• Monorepo managing multiple npm packages (components, graph, utils)
• Kustomize overlays for environment-specific Kubernetes configs
• Infrastructure as Code (Tekton CI/CD pipelines)
d. Key technologies & frameworks:
• Frontend: React, Vite, Storybook, Cypress
• Backend: Go, Gorilla Mux router (pkg/router), client-go for k8s
• Deployment: Kubernetes, Kustomize, Tekton Pipelines & Triggers
• CI: GitHub Actions, Tekton CI pipelines
Elements
– Blue for user-facing components (Browser, SPA)
– Green for backend services (API server)
– Orange for infrastructure (Kubernetes, Tekton)
– Gray for CI/CD and external services