Applications
Applications › Applications groups the Deployments, StatefulSets, DaemonSets and CronJobs in the namespaces you’re looking at into applications. Applications that need attention come first, and each one has its own page.
How workloads are grouped
Section titled “How workloads are grouped”Within a namespace, KubeGlass puts a workload into the first of these it has:
- The Helm release that installed it (the
meta.helm.sh/release-nameannotation), so all of a chart’s parts are one application, even when the chart labels them differently. - Its Argo CD application (the
argocd.argoproj.io/instancelabel or tracking annotation). - The
app.kubernetes.io/part-of,app.kubernetes.io/instanceorapp.kubernetes.io/namelabel, thenappork8s-app. - Its own name.
A Helm release and a plain Deployment with the same name stay separate.
The list
Section titled “The list”Each row shows:
- how many of its pods are ready, and their restarts;
- what is wrong with its pods, in the same words as the resource lists. Hover over the problem for what it means and the cluster’s own message;
- its workloads, and where it came from: a Helm release (with a link to it), an Argo CD application or Flux;
- its version, from
app.kubernetes.io/versionor else the image tag; - the addresses its ingresses serve, for Services that select its pods.
System namespaces (kube-*, openshift-* and names ending in -system) are hidden when you look at all namespaces; the button above the table shows them. Choosing one of those namespaces shows its applications as usual. Need attention shows only applications with a problem, and the filter matches application, namespace and workload names.
An application’s page
Section titled “An application’s page”Clicking a row opens the application’s page at /apps/<namespace>/<name>. It starts with a verdict in one line, such as “Running. Every pod is ready.”, “Partly working: 2 of 3 pods are ready.” or “Rolling out: some pods are starting or being replaced.”, then:
- Needs attention: the problems of its objects, as on the Overview, with their fixes.
- Workloads: each one with its ready count and image, linking to its page.
- Pods: every pod with its status, restarts and node, and links to its logs and a shell.
- Logs: the logs of the workload most worth reading, usually the one with a problem, with a choice of the others.
- Addresses: the URLs its ingresses serve, and the Services that select its pods with their type, ports and external addresses. If no Service selects them, the page says how to add one.
- Recent changes: the changes KubeGlass recorded to its objects.
Restart restarts all its Deployments, StatefulSets and DaemonSets after asking, the way kubectl rollout restart does. For a Helm release, Upgrade opens the release’s view in Helm releases and Roll back opens its History. All three are hidden in read-only mode.
When two applications in a namespace have the same name, for example a Helm release and an Argo CD application, the page links to the other one.