Announcement
Bahriya Kubernetes Engine 2.0.0 is released
Bahriya Kubernetes Engine 2.0.0 is released. It is a major release, and under BKE’s release rules a major is the only kind that may move the Kubernetes minor — so it moves the Kubernetes minor, and it moves nothing else. Every bundled component is identical to the release before it.
That restraint is the point of the release rules. An upgrade that moved Kubernetes and seven components at once would make any failure ambiguous, and it is the ambiguity rather than the failure that costs an operations team the day. Under BKE, a patch release moves component patches and never drains a node; only a major moves Kubernetes, and it arrives alone. Exact versions — every one of them pinned to a patch, never a moving minor — are in the release notes in the Mamluk Console.
Your configuration is yours, and upgrades ask
The BKE product page has carried a commitment since the beginning: every component’s configuration is a file you own and may edit, and upgrades show you the difference between what you run and what is proposed, then wait for you to agree. With 2.0.0 that commitment is behaviour.
Each component’s configuration lives on your control-plane node as a file you may edit freely. Before an upgrade commits, BKE compares what you are running, what you have written, and what the new release proposes — structurally, key by key, so your comments and your formatting survive — and reports what would change. Nothing is applied without --commit, and your changes are never silently overwritten. Where your edit and ours touch the same key, the upgrade stops and says so rather than choosing for you.
Cluster login, through your identity provider
A 2.0.0 cluster can be created with API-server authentication against your own OIDC identity provider — Entra ID, Okta, Keycloak and their peers. Your people log in as themselves, audit logs carry their names, and all access is granted through group membership mapped onto Kubernetes’ built-in roles. BKE distributes no kubeconfigs and stores no credentials; the kubeconfig your users hold references the issuer, not a secret.
Trial it
2.0.0 is the release the self-service trial issues: a 14-day licence, the full distribution with no editions and no feature gates, on your own machines. Create an account, issue the licence, paste one command onto a node.
For existing customers, the upgrade path and its one hard prerequisite — the etcd snapshot, because a Kubernetes minor cannot be downgraded — are documented in the console. A major drains nodes; plan it as the maintenance window it is.