Quick answer: Weave Scope is no longer maintained. For a current Kubernetes replacement, use CloudMaps when you need a live, agent-free cluster map; KubeView for a lightweight read-only resource graph; Kiali for Istio traffic; or KubeDiagrams for exportable architecture diagrams. There is no official one-to-one successor, so choose by use case and deployment model.
See CloudMaps, the agent-free live map in K8Studio
Is Weave Scope still maintained?
No. The official Weave Scope repository labels the project deprecated and states that it is no longer maintained. GitHub lists the latest Scope release as version 1.13.2 from April 2021.
Weave Scope was influential because it automatically mapped containers, hosts, and processes. That history still matters, but an unmaintained observability component creates practical questions around new Kubernetes releases, container runtimes, browser dependencies, and security fixes. Existing installations should be treated as legacy software and given a migration plan.
What should a Scope replacement preserve?
Before comparing products, write down the parts of Scope that your team actually uses:
- A live view rather than a diagram that must be regenerated.
- Fast movement from an overview into a specific workload or pod.
- Relationships between applications, Services, routes, and storage.
- Health and status visible without opening every object.
- Local or self-controlled data processing.
- A deployment model your security team accepts.
The last point is important. Scope used probes to collect topology and process data. Some teams want the same depth and accept an in-cluster component; others now require a visualization that reads the standard Kubernetes API without adding agents.
Weave Scope alternatives compared
| Alternative | Main use case | Live | In-cluster agent required | Important difference from Scope |
|---|---|---|---|---|
| K8Studio CloudMaps | Operational cluster map | Yes | No | Desktop, zoom-based aggregation, Kubernetes object relationships |
| KubeView | Read-only resource graph | Yes | No probe model | Focused open-source graph connected to the Kubernetes API |
| Kiali | Istio service-mesh traffic | Yes | Uses mesh telemetry | Traffic and mesh health rather than a general cluster map |
| KubeDiagrams | Architecture documentation | On demand | No continuous agent | Generates exportable diagrams from files or cluster state |
| Headlamp | General cluster administration | Yes | Deployment-dependent | Broad, extensible Kubernetes UI rather than a Scope-style map |
1. CloudMaps: a live, agent-free replacement
CloudMaps is the closest option in this list when the goal is a navigable live map, but its model is Kubernetes-native rather than process-centric. It shows namespaces as distinct areas and progressively reveals workloads, pods, Services, Ingresses, Gateway API routes, PVCs, policies, and dependencies as you zoom.
K8Studio runs on macOS, Windows, and Linux and connects through your existing kubeconfig. CloudMaps does not install probes, DaemonSets, sidecars, operators, CRDs, or collectors. Cluster data is interpreted and rendered in the desktop application.
That design is useful for organizations that do not want another privileged component in production or need to work in air-gapped networks. It also changes the scale behavior: CloudMaps aggregates detail by zoom level and only draws the relevant viewport instead of placing every object in one fixed graph. The current beta is designed and tested for clusters with 5,000 or more workloads.
Best fit: teams replacing Scope's visual exploration with a maintained, agent-free Kubernetes map.
2. KubeView: a lightweight open-source graph
KubeView provides a secure, read-only graph of Kubernetes resources and derived relationships. Its v2 implementation receives real-time updates and focuses specifically on cluster visualization.
KubeView is a good starting point if your priority is an open-source graph with a narrow operational scope. Test it with your real cluster size and resource mix, especially if you rely on many custom resources or dense cross-resource relationships.
Best fit: teams that want a focused, read-only relationship graph.
3. Kiali: use it when Scope was mainly a traffic map
Kiali is purpose-built for Istio. It visualizes service traffic and combines request rates, errors, latency, and mesh configuration.
If your Scope workflow centered on live service-to-service communication, Kiali may be the more precise replacement. It is not intended to be a general map of all Kubernetes objects, and it depends on the service-mesh telemetry available in your environment.
Best fit: teams running Istio that need traffic and mesh diagnostics.
4. KubeDiagrams: replace screenshots with generated documentation
KubeDiagrams creates architecture diagrams from manifests, Kustomize files, Helm charts, Helmfiles, and actual cluster state. It supports custom resources and can export to formats such as SVG, PNG, PDF, draw.io, and DOT.
This is not a continuously updating Scope replacement. It is better when the real requirement is a repeatable architecture artifact for reviews, onboarding, or documentation.
Best fit: teams that need generated, shareable Kubernetes diagrams.
5. Headlamp: replace the broader dashboard workflow
Headlamp is an active and extensible Kubernetes web UI. It is broader than a topology map and supports general resource administration and plugins.
Choose it when Scope was one part of a larger need for a browser-based Kubernetes dashboard. If topology is the deciding requirement, evaluate the available graph experience separately from the rest of the UI.
Best fit: teams prioritizing an extensible web administration interface.
Migration checklist
- Inventory the current Scope deployment. Record probes, permissions, exposed ports, dashboards, and links that depend on it.
- List the questions users ask. Separate cluster topology, traffic analysis, process inspection, and general administration.
- Choose the new data boundary. Decide whether in-cluster agents are allowed and whether data may leave the workstation or cluster network.
- Test against production-like scale. Measure initial load, updates, graph readability, pan and zoom, and CPU and memory use.
- Validate object coverage. Include Deployments, StatefulSets, DaemonSets, Jobs, Services, Ingresses, Gateway API resources, PVCs, policies, and required CRDs.
- Run both tools briefly. Confirm that common incident and onboarding workflows work before removing Scope.
- Remove legacy access. Delete unused probes, service accounts, roles, Services, and ingress rules after the migration.
Frequently asked questions
What replaced Weave Scope for Kubernetes?
There is no official successor. CloudMaps covers live, agent-free cluster mapping; KubeView covers lightweight resource graphs; Kiali covers Istio traffic; and KubeDiagrams covers generated architecture documentation.
What is an agent-free Weave Scope alternative?
K8Studio CloudMaps is agent-free. It reads the Kubernetes API through kubeconfig and does not install a probe, DaemonSet, sidecar, operator, or collector.
Can I use Weave Scope in 2026?
An existing installation may still run, but the official project is no longer maintained. Evaluate compatibility and security risk, and plan a move to a maintained tool.
Can CloudMaps handle a large cluster?
CloudMaps uses zoom-based aggregation, spatial indexing, and viewport rendering. The current beta is designed and tested for clusters with 5,000 or more workloads.