Vizxr v1.1.0 reworked the whole app around a Lens-style layout. This post covers what changed, and is upfront about which screens are finished and which are still placeholders.

✨ What shipped in v1.1.0

  • Global scope bar: cluster-wide and namespaced resources are now filtered separately, with a searchable namespace picker. That unblocked Apply YAML and the Events feed from any screen.
  • Resource inspector: a slide-over panel with the object's overview, containers and pod spec, its live events, and the manifest YAML.
  • CRD explorer: discover every CustomResourceDefinition and drill into its instances.
  • Helm on k3s: browse releases, inspect revisions and values, roll back or uninstall.
  • New identity: a vector logo and Play Store banner in the AI2TH design language.

🧭 Honest status

We would rather tell you now than have you find out mid-incident.

Feature Status
Resource browsing, CRDs ✅ Real, live API calls
Log streaming ✅ Real (follow=true)
Events ✅ Real
Apply YAML (create or update) ✅ Real
Helm releases ✅ Real on k3s (HelmChart resources); classic Helm v3 releases not yet
Cluster CPU and memory gauges 🚧 Placeholder values; wiring to metrics.k8s.io is next
Pod exec terminal 🚧 UI only; the real exec over the API's WebSocket stream is in progress
Port forwarding 🚧 Not implemented yet

🗺️ What's next

  1. Real metrics from metrics-server (metrics.k8s.io/v1beta1) for nodes and pods
  2. Real pod exec over the Kubernetes exec WebSocket protocol, into the xterm view that is already there
  3. Port forwarding to open a pod's web UI in Chrome on the phone
  4. Classic Helm releases (the sh.helm.release.v1 secrets), not just k3s HelmCharts

🤝 Help wanted

The client is a single Dart file with clear seams. If you know the exec or port-forward stream protocols, a pull request is very welcome.

📥 Get Vizxr