Repository navigation
What's new
Events follow the object live. Asked for while testing 2.23.3. The Events of a pod or workload drawer used to be read again only when the object itself changed, so a repeated Warning or a growing BackOff count showed only after reopening.
- The pod and workload (Deployment, StatefulSet, DaemonSet) drawers, and the list behind a row's Events button, read the last hour of events and then follow the object's new events as they happen. They use the namespace's
/ws/eventsstream, the one Live events uses, filtered to that object; permissions are checked by the server as before. - A new event is added, briefly highlighted and announced to screen readers. A repeat updates its row in place (
×5and its time). - ● Live / Reconnecting… shows the stream state. After a dropped connection, the list is read again to fill the gap.
- The row Events dialog shows the same list as the drawers (warnings first, count, age) instead of raw JSON.
/ws/eventsframes of Kubernetes events carrycount. This is an addition only; the OpenAPI description lists the frames.
Upgrading
Replace the image: there is no change to the API's paths, the database, the manifests or deploy/elk. Rolling back to 2.23.3 works.
Tested on Zenia nonprod with the :dev-194 image and a throwaway namespace:
- a new event on a pod appeared and was announced without reopening the drawer, and its repeat became
×4in the same row; - scaling a Deployment made
ScalingReplicaSetappear in its open drawer; - the Events dialog listed the events live;
- the API checklist and the browser checks (124: light / dark, EN / TR, keyboard, axe) passed;
- this image passed a Docker smoke test.
Image
ghcr.io/vurulkan/kubernetes-openconsole:2.23.4 (= :latest, same digest sha256:80afd955…; amd64 + arm64), with signed provenance and SBOM:
gh attestation verify oci://ghcr.io/vurulkan/kubernetes-openconsole:2.23.4 --repo vurulkan/kubernetes-openconsole
🤖 Generated with Claude Code