Bahriya Kubernetes Engine 2.5.1 is released. It is a patch release: Netdata’s chart moves one patch, and no Kubernetes, containerd or Calico version moves. The release notes in the Mamluk Console list each change and its effect.
No node drains. Clusters on 2.5.0 upgrade by running apply.sh once.
Netdata v2.12.3
Netdata moves to v2.12.3, which fixes several crashes, among them one in alarm evaluation and one when a node’s agent reconnects to the parent, and hardens access lists and the parsing of URLs. Every Netdata pod restarts once during the upgrade, so its charts show a short gap, and a node can be missing from the parent for up to ten minutes, or fifteen where the parent holds ten or more nodes, while its agent waits to reconnect. The upgrade page in the documentation explains why.
Alarms for the Compliance App
The Netdata parent now carries alarms for the Compliance App, the application of the Compliance and Assurance Convoy: when it stops writing its metrics, when a regime has no evidence run as recent as its schedule requires, when one of its volumes is filling, and when it has no ready replica. On a cluster without the Compliance App, none of them is raised. They are delivered only to an alarm channel you turn on.
Each alarm depends on the Netdata agent that collects its chart. While the agent that reads Kubernetes objects is stopped, the alarm for no ready replica is not evaluated, so watch the Netdata pods’ own health as you would any other component’s.
A check of cluster DNS from every node
A node can be Ready while Pods on it cannot resolve a single cluster name. The new tools/dnscheck.sh runs one short-lived Pod on each node in turn, looks up cluster names from it, and reports each node as ok or FAIL. It reads the cluster’s own DNS domain, so it works on a cluster built with a domain other than cluster.local. Without --commit it creates nothing and says what it would check.
Upgrading
From 2.5.0, run apply.sh once from a control-plane node. As with every BKE upgrade, it first reports each change against your own values files and changes nothing until you run it with --commit. From 2.4.x, 2.5.1 is a minor upgrade and follows the full sequence in the documentation.