dev-tools 5 min read

Crossview - Crossplane UI Dashboard for Kubernetes

Open-source dashboard for managing Crossplane resources in Kubernetes. Real-time monitoring, multi-cluster support, Go + React.

By
Share: X in
Crossview - Crossplane UI Dashboard

TL;DR

TL;DR: Crossview is an open-source React dashboard for managing Crossplane resources in Kubernetes — real-time monitoring, multi-cluster switching, and a Go backend, deployable via Helm or Docker.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

What Is Crossview?

Crossview is an open-source dashboard for managing and monitoring Crossplane resources in Kubernetes. Crossplane is an open-source framework that treats Kubernetes as a universal control plane for infrastructure — letting you provision and manage cloud resources (AWS, GCP, Azure, etc.) through Kubernetes Custom Resource Definitions (CRDs). If you run Crossplane in production, Crossview gives you a visual interface to browse, search, and inspect those resources without writing kubectl commands.

The project is maintained by corpobit under the crossplane-contrib GitHub organization. As of June 2026 it has 253 GitHub stars and is actively maintained with a recent push on June 29, 2026.

Setup Workflow

Prerequisites

  • A running Kubernetes cluster with Crossplane installed
  • kubectl configured to access the cluster
  • Helm 3 (for Helm installation), or Docker / Docker Compose (alternative)

Option 1: Install via Helm

Add the Crossview Helm repository and install with a release name of your choice:

helm repo add crossview https://charts.crossplane.io/crossview
helm repo update
helm install crossview crossview/crossview \
  --namespace crossview-system \
  --create-namespace

After installation, forward the port to access the dashboard locally:

kubectl port-forward -n crossview-system svc/crossview 8080:8080

Open http://localhost:8080 in your browser.

Option 2: Run with Docker

Build the Docker image and run with your kubeconfig mounted:

docker build -t crossview .
docker run -p 8080:8080 \
  -v ~/.kube/config:/root/.kube/config \
  -e KUBECONFIG=/root/.kube/config \
  crossview

Option 3: Docker Compose

docker compose up -d

Deeper Analysis

Architecture

Crossview has two main components:

  • Frontend: React with Chakra UI for the interface, supporting dark mode. Runs in the browser and communicates with the backend over REST and WebSocket.
  • Backend: Built in Go using the Gin framework. Connects to your Kubernetes cluster via the standard client-go library and proxies API requests.

The backend watches Kubernetes resources in real-time using Kubernetes Informers, so the dashboard updates without a page refresh.

Key Features

From the README:

  • Real-Time Resource Watching — event-driven updates via Kubernetes Informers; no polling
  • Multi-Cluster Support — switch between multiple Kubernetes contexts from the UI
  • Resource Visualization — browse Crossplane resources: Providers, XRDs (CompositeResourceDefinitions), Compositions, and Claims
  • Resource Details — view status conditions, metadata, events, and resource relationships
  • Modern UI — React + Chakra UI with dark mode
  • SSO Integration — OIDC and SAML authentication support
  • High Performance — Go + Gin backend handles large clusters efficiently

Comparison with Alternatives

If you run Crossplane, the default management interface is kubectl or Octant’s Crossplane plugin. Crossview is purpose-built for Crossplane — it understands the resource model (XRDs, Compositions, Claims) and presents them natively rather than as raw YAML.

Compared to other infrastructure-as-code dashboards (like Crossplane’s own Compass), Crossview is a lightweight, self-hosted option with no mandatory cloud dependency.

Practical Evaluation Checklist

  • [ ] Installs cleanly on a standard Kubernetes cluster (Helm chart available)
  • [ ] Frontend loads and displays Crossplane resources within 10 seconds
  • [ ] Multi-cluster context switching works from the UI
  • [ ] Real-time updates reflect changes without manual refresh
  • [ ] Dark mode toggle works
  • [ ] Resource detail view shows status conditions and events
  • [ ] SSO (OIDC) integration configurable for enterprise environments
  • [ ] No required external database — state is fetched live from the cluster

Security Notes

  • The backend reads your kubeconfig to connect to the cluster. Treat the deployment with the same sensitivity as kubectl access.
  • SSO support (OIDC/SAML) allows integration with enterprise identity providers — recommended for shared clusters.
  • No data leaves your cluster by default; Crossview proxies all API calls through its backend.
  • The Artifact Hub badge indicates the Helm chart is published through a standard channel.

FAQ

Q: Does Crossview require a database? A: No. Crossview fetches all resource state live from the Kubernetes API. There is no external state store.

Q: Can I use it without Crossplane installed? A: The dashboard loads without Crossplane, but there is nothing to display until Crossplane CRDs are present in the cluster.

Q: Does it support managed Crossplane services like Upbound? A: Crossview connects to any Kubernetes cluster where Crossplane is installed, including managed distributions. You point it at a kubeconfig context.

Q: Is there a hosted / SaaS version? A: No. Crossview is fully self-hosted. You deploy it to your own cluster.

Conclusion

Crossview fills a gap in the Crossplane ecosystem: a dedicated, visual interface for inspecting managed resources across one or many clusters. With a Go backend for performance, React/Chakra UI for a clean experience, and Helm/Docker deployment options, it is a practical choice for teams running Crossplane at scale. The SSO integration also makes it viable for enterprise environments where a CLI-only tool would not work.

If you are using Crossplane in production, Crossview is worth a look. Install it with Helm, point it at your cluster, and you have an instant visibility dashboard with no external dependencies.

Source and Accuracy Notes