Repository navigation
battery-operator v0.3.0: Kubernetes v1.36, containerd v2 and flintlock v0.16 on the Host Image
The Host Image moves to Kubernetes v1.36 and containerd v2, with flintlock v0.16.0.
| Component | v0.2.x | v0.3.0 |
|---|---|---|
| Kubernetes (kubelet, kubeadm) | v1.35.8 | v1.36.3 |
| containerd | v1.7.22 | v2.2.9 |
| flintlock | v0.15.2 | v0.16.0 |
| Firecracker | v1.10.1 | v1.16.1 |
| Cloud Hypervisor | v41.0 | v48.0 |
- containerd's configuration is now in v2's format (
version = 3). The thin pool snapshotter for flintlock is unchanged. - flintlockd and the kubelet's image pulls read registry configuration from
/etc/containerd/certs.d(HI-081). The image ships none, so pulls work as before.hostimage/README.mdsays how to add a mirror, a CA or a credential. - The example Host pool in
config/capiuses Kubernetes v1.36.3. Pools that boot a v0.2.x AMI keep v1.35.8. With the AWS cloud controller manager, use v1.36.1 for v1.36. - A Host booted from the arm64 image joined a v1.36.3 kubeadm cluster and ran a Pool, claims, the guest network and a flintlockd restart (
hack/kubeadm-host).
Not proven yet: MicroVMs on Cloud Hypervisor (#202). Cloud Hypervisor starts, but the trial's guest kernel lacks virtio-pci.
The Operator and the Exec Agent have not changed since v0.2.1.
Manifests artifact:
ghcr.io/phoban01/battery-operator/manifests:v0.3.0@sha256:f714b72f094d8bde1a20410e8178d997d25d5acab46cf9bf46cb6f6ea46647f1
flux pull artifact oci://ghcr.io/phoban01/battery-operator/manifests:v0.3.0 --output ./battery-operator
Images, for linux/amd64 and linux/arm64:
ghcr.io/phoban01/battery-operator:v0.3.0ghcr.io/phoban01/battery-operator/exec-agent:v0.3.0ghcr.io/phoban01/battery-operator/host-image:v0.3.0
To make an AMI: make host-image-ami HOST_IMG=ghcr.io/phoban01/battery-operator/host-image:v0.3.0 HOST_IMAGE_AMI_ARGS="--bucket ... --region ...". AMIs are x86_64 only.