Skip to content

v1.0.3

Choose a tag to compare

View all tags
@akash-cloudtech akash-cloudtech released this 22 Jul 20:23
· 3 commits to main since this release
v1.0.3
287ee9b

K8s Rizz Check v1.0.3

Bug fix release. Real-world testing surfaced a batch of resource kinds showing status "Unknown" in the resource tree even when they were completely healthy, and in some cases dragging their parent's status down to a false "warn" along with them.

What was wrong

A handful of built-in Kubernetes kinds don't report health through status.conditions the way Deployment does. They either use their own condition types, plain replica counts, or a different field entirely. The dashboard only knew how to read the Deployment-style conditions, so anything else fell back to a generic "Unknown".

Fixed

  • ReplicaSet, StatefulSet, DaemonSet: now correctly show "Available" when fully ready (was cascading a false warn onto otherwise-healthy Deployments)
  • CronJob: now shows a healthy baseline instead of "Unknown" (real failures still surface through its Jobs/Pods, same as before)
  • Ingress: reflects whether a load balancer has actually been provisioned
  • HorizontalPodAutoscaler: reads its actual scaling-active condition instead of falling through
  • PodDisruptionBudget: reads its disruption-allowed condition (or healthy pod counts on older clusters)
  • PersistentVolumeClaim: now shows its real Bound/Pending/Lost phase
  • Service: no longer shows "Unknown" for ordinary ClusterIP/NodePort services; LoadBalancer-type services reflect actual provisioning status

No configuration changes needed. Existing config.yaml files keep working as-is.

Assets 7
Loading