K8Studio 4.0.0
Version 4.0.0
A major CloudMaps release. CloudMaps is the Google Maps for Kubernetes clusters, helping teams see everything, spot problems, and understand large environments in seconds. This release also adds first-class Gateway API visibility, redesigned workload and Pod details, clearer status classification, improved port-forward management, and timeline polish.
Highlights
CloudMaps
- CloudMaps is the headline improvement in K8Studio 4.0.0: a Google Maps for Kubernetes clusters, built to help teams see everything, spot problems, and understand large environments in seconds.
- CloudMaps is designed for huge clusters, including environments with 5,000+ workloads, where traditional trees and tables become too slow to reason about on their own.
- Topology views are easier to use during daily troubleshooting, with selected objects, related workloads, Services, Pods, Nodes, ports, routes, policies, and dependencies easier to follow.
- Gateway API support is integrated into the CloudMaps experience so modern ingress and routing resources can be understood in context instead of isolated YAML.
- Resource relationships are easier to inspect from detail views, helping users move from a workload to its networking, policies, routes, Pods, and related objects faster.
- CloudMaps and object topology now fit more naturally into the troubleshooting flow, with Topology placed after Logs and before Events in object details.
- Timeline polish also supports CloudMaps investigations by making dense event rows easier to read when tracing what happened around a selected resource.
Gateway API
- Added a dedicated Gateway section in the cluster tree for Gateway API resources when the API is 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 in a focused overview.
- 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 so cross-namespace access is easier to understand.
- 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
- Workload status now uses clearer customer-facing 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 so users can distinguish temporary startup from a real rollout stop.
- Crash loops, ReplicaFailure, and hard container errors continue to appear as Degraded.
- Status colors now match the existing Kubernetes object icon/status palette across healthy, warning, pending, blocked, and degraded states.
- Replica chips now include a Pending state so the status card better explains what is happening at a glance.
Resource Details
- Deployment details make better use of horizontal space, with compact Status, Strategy, Resources and Limits, and Pods sections.
- Deployment Pod grids use the 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 port-forward 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 for a more natural troubleshooting flow.
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.