Skip to content

4.0.0

Choose a tag to compare

View all tags
@guiqui guiqui released this 15 Jul 08:05
v4.0.0
5cda859
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

K8Studio 4.0.0

Release date: 2026-07-14

K8Studio 4.0.0 is a major CloudMaps release.

CloudMaps is the Google Maps for Kubernetes clusters: see everything, spot problems, and understand your cluster in seconds. It is designed for large environments, including clusters with 5,000+ workloads, where traditional trees and tables are not enough on their own.

This release also adds first-class Gateway API visibility, redesigned workload and Pod details, clearer workload status classification, improved port-forward management, and timeline polish.

Highlights

  • CloudMaps is now the center of the K8Studio 4.0 experience, giving teams a visual way to explore Kubernetes relationships, routing, dependencies, and infrastructure context.
  • Gateway API resources now have their own navigation area, grids, and detail views for modern Kubernetes ingress and routing workflows.
  • Gateways, GatewayClasses, HTTPRoutes, GRPCRoutes, and ReferenceGrants are easier to inspect with focused overview pages instead of raw YAML-first views.
  • Workload status is more precise with Healthy, Scaling, Updating, Pending, Blocked, and Degraded states, including better handling for Pending Pods.
  • Deployment and Pod details use space more efficiently with redesigned status, strategy, resource, container, labels, annotations, ports, and policy sections.
  • Port forwarding is easier to manage from resource actions with active-state indicators, inline creation, and quick removal.
  • Timeline event labels behave better in dense rows, avoiding occasional overlap between lifecycle labels.

CloudMaps

  • Added CloudMaps as the headline K8Studio 4.0 experience: a Google Maps-style way to monitor and explore Kubernetes clusters.
  • Improved visual investigation for huge clusters, including environments with 5,000+ workloads.
  • Made Kubernetes relationships easier to follow across selected objects, workloads, Services, Pods, Nodes, ports, routes, policies, storage, and dependencies.
  • Integrated Gateway API resources into the CloudMaps troubleshooting flow so modern ingress and routing resources can be understood in context.
  • Moved Topology after Logs and before Events in object details for a more natural investigation flow.
  • Improved dense timeline readability so CloudMaps investigations are easier to correlate with recent cluster activity.

Gateway API

  • Added a dedicated Gateway section in the cluster tree when Gateway API resources are available in the cluster.
  • Added grids and resource views for Gateways, GatewayClasses, HTTPRoutes, GRPCRoutes, ReferenceGrants, BackendTLSPolicies, and BackendTrafficPolicies.
  • Gateway details now highlight gatewayClassName, listeners, listener ports, addresses, and conditions.
  • GatewayClass details now show controller information, parameters, and conditions without forcing users into raw YAML first.
  • HTTPRoute and GRPCRoute details now show hostnames, parent refs, route rules, matches, filters, backend refs, ports, weights, and route conditions.
  • ReferenceGrant details now show allowed From and To references in a clean overview.
  • Gateway condition types are color-coded consistently with the rest of the workload and resource status experience.
  • Gateway API resources use a dedicated Gateway icon so they are easier to distinguish from general networking objects.

Workload Status

  • Added clearer customer-facing workload states: Healthy, Scaling, Updating, Pending, Blocked, and Degraded.
  • Deployments with non-crashing Pending Pods are shown as Pending instead of being marked Degraded too early.
  • Scheduling failures, progress-deadline failures, and blocked rollouts are shown as Blocked.
  • Crash loops, ReplicaFailure, and hard container errors continue to appear as Degraded.
  • Status colors now match the existing Kubernetes object icon and status palette.
  • Replica chips now include a Pending state so status cards explain rollout state more clearly.

Resource Details

  • Deployment details now make better use of horizontal space with compact Status, Strategy, Resources and Limits, and Pods sections.
  • Deployment Pod grids use available width and height more efficiently while avoiding large empty areas.
  • Pod details now start with a compact Pod Details card that groups status, conditions, scheduling, timing, and access information.
  • Labels and annotations are moved lower in the page so operational status, resources, ports, policies, and containers are easier to reach first.
  • Container cards now sit side by side with Network Policies and Port Forwarding when space allows.
  • Container information popovers are more readable, with clearer labels, values, commands, ports, environment variables, probes, security context, and mounts.
  • Conditions are now labeled as Conditions instead of Health, and condition types are color-coded.
  • Light-mode detail buttons have stronger contrast and no longer look disabled.

Port Forwarding

  • Port forwarding now uses a clearer two-arrow action icon with an active-state dot.
  • The port-forward action shows whether a resource has active port forwards with a subtle green or grey indicator.
  • Hovering the action opens a compact popover with active sessions, local URLs, remote/local port information, and remove controls.
  • New port forwards can be created inline from the popover when none are active.
  • The detail-page Port Forward box now renders only when port forwarding exists and stays compact beside related networking information.
  • Long active port-forward lists are scrollable so the surrounding detail layout stays stable.

Timeline and Topology

  • Timeline duration labels now avoid overlapping in dense rows such as Started, Created, Pulled, and SuccessfulCreate event clusters.
  • Extra colliding timeline markers are summarized behind compact counts instead of stacking labels on top of each other.
  • Narrow duration markers now render more compactly so event labels do not collide with count badges.
  • Topology tabs now sit after Logs and before Events in object details.

Fixes

  • Fixed Service details that could crash when rendering object-shaped status fields such as loadBalancer.
  • Fixed missing component views for newly supported Gateway API resources.
  • Fixed Gateway, GatewayClass, HTTPRoute, GRPCRoute, and ReferenceGrant detail pages falling back to raw or missing views.
  • Fixed workload status wording and color mismatches when a Deployment had Pending Pods.
  • Fixed occasional timeline label overlap in dense event rows.
  • Fixed several layout issues in Pod and Deployment details where cards, grids, or long container paths could waste space or overflow.
Assets 19
Loading