Bahriya Kubernetes Engine 2.1.1 is released. It is a patch release: every version BKE pins is the same as in 2.1.0, and what changes is the configuration BKE applies to three of its components. The release notes in the Mamluk Console list each change and its effect.
Kong now has a disruption budget
BKE 2.1.0 set a limit for Kong’s PodDisruptionBudget without enabling the budget, so no budget was created. In 2.1.1 it is created. A node drain, or any other voluntary disruption, now takes at most half of Kong’s pods at a time, so ingress traffic continues to be served while a node is maintained.
Settings the components ignored are removed
Three settings had no effect. Kong does not read one of the connection settings BKE set; the limit Kong applies comes from a different setting, which is unchanged. Three budget limits for cert-manager created nothing, because no budget was enabled. Netdata reported one plugin setting as unused. Each is removed, so the configuration BKE applies now describes only what the components do.
cert-manager still has no disruption budget, and this is deliberate. Each of its parts runs a single replica, and a budget that required one replica to remain available would stop every node drain. A budget will come with a second replica, in a later minor release.
Upgrading
From 2.1.0, the upgrade is apply.sh alone. No node software moves, so there is no upgrade.sh step and no node drains. Kong’s pods and the Netdata parent restart once, because their configuration changes.
As with every BKE upgrade, apply.sh first reports each change against your own values files and changes nothing until you run it with --commit. A setting you have changed yourself is kept. Where your change and BKE’s touch the same setting, the report stops and shows both, so that you decide.
Clusters on 2.0.x move to 2.1.1 directly, following the full sequence for a minor upgrade in the documentation.