Release v0.6.0

What's new

k8s-dqlite removed as a datastore option

⚠️ This is a critical breaking change. The k8s-dqlite datastore option has been removed from CAPI-CK8s starting with v0.6.0 (#203).

k8s-dqlite was deprecated in Canonical Kubernetes 1.35 and will be removed entirely in Canonical Kubernetes 1.36. As a result, this provider no longer supports k8s-dqlite as a datastore backend.

Impact

• Clusters using k8s-dqlite cannot upgrade from v0.5.x to v0.6.0.
• There is no migration path from k8s-dqlite to etcd for existing clusters.

Recommended Actions

If your cluster is currently using k8s-dqlite as the datastore:

1. Do not upgrade: Continue using CAPI-CK8s v0.5.x if you need to maintain your existing cluster with k8s-dqlite.
2. Create a new cluster: If you want to use v0.6.0+, provision a new cluster with etcd as the datastore and migrate your workloads.

All new clusters provisioned with v0.6.0 and later will use etcd as the datastore.

Bug fixes

• Fix stray quotes in --provider-id for OpenStack templates, which was preventing control plane nodes from bootstrapping correctly (#202) - Fixes #178
• Update Incus version to v0.8.3 to fix failing CI (#200)
• Fix snap install to not use the --dangerous flag, which was breaking rolling upgrades for minor k8s versions (#193)

Security

• Bump golang.org/x/crypto from 0.36.0 to 0.45.0

Chores & CI

• Preparation for v0.6.0 release (204)
• Remove CODEOWNERS file (#198)
• Bump staticcheck to latest version for TICS (#196)
• Remove harden-runner from CI (#187)

New Contributors

• @ktsakalozos made their first contribution in #198
• @jorgehrn-cloudfiles made their first contribution in #202

Full Changelog

v0.5.1...v0.6.0