Skip to content

Releases: innobead/kubefire

v0.3.10

16 Apr 00:22
Compare
Choose a tag to compare

v0.3.9

15 Apr 05:45
Compare
Choose a tag to compare

v0.3.8

21 Jun 14:44
Compare
Choose a tag to compare
  • Use the builtin node name as the K8s node name for k3s, kubeadm and rke2

v0.3.7

17 Jun 12:20
Compare
Choose a tag to compare
  • Upgrade containerd to v1.6.6
  • Upgrade ignite to v0.10.0
  • Upgrade CNI plugins to v1.1.1
  • Upgrade runc to v1.1.3
  • Fix K0s deployment because of some deprecated command options
  • Fix kubectl log not working on the default K3s deployment
  • Remove deprecated rancherd and rke support

v0.3.6

02 May 19:08
Compare
Choose a tag to compare
  • [enhancement] Update cilium to 1.9 for kubeadm bootstrapper #48
  • [enhancement] Support cluseter semver w/ prerelease #47

Notes

Upgrade kubefire and the required dependencies

kubefire version
Version: v0.3.4
Build: 2608d45-20210107093257kubefire info
CONTAINERD	IGNITE	CNI   	RUNC      	CNIPLUGIN                 
v1.4.1    	v0.8.0	v0.8.7	1.0.0-rc92	0.4.0/kubefire-cni-bridge	huber update kubefire
Updating kubefire (version: v0.3.4, source: github) to kubefire (version: v0.3.6, source: github)
Downloading package artifacts from github "https://github.com/innobead/kubefire"
Setting kubefire (version: v0.3.6, source: github) as the current package
Installed executables:
 - /home/davidko/.huber/bin/kubefire
kubefire updatedkubefire version
Version: v0.3.6
Build: 9413383-20210502190639kubefire install
...kubefire info
CONTAINERD	IGNITE	CNI   	RUNC      	CNIPLUGIN                 
v1.4.4    	v0.9.0	v0.9.1	1.0.0-rc93	0.4.0/kubefire-cni-bridge	

Support RancherD bootstrapper

kubefire cluster create demo -b rancherd 

Support pre-release cluster bootstrapping

kubefire cluster create demo -b k3s -v v1.21.0-rc1+k3s1

v0.3.5

02 May 13:37
Compare
Choose a tag to compare
  • [bug] Failed to deploy the latest version (1.21) K3s cluster #46
  • [enhancement] Update dependent binaries #45
  • [enhancement] Update containerd (1.4.3) and runc (1.0.0-rc93) #43
  • [enhancement] Support RancherD deployment #44

v0.3.4

07 Jan 09:47
Compare
Choose a tag to compare
  • [enhancement] Support K0s deployment #42
  • [enhancement] Support RKE2 for development purpose #41

Notes

  • Please firstly run kubefire cache delete to delete some deprecated cache format before running cluster operations

  • RKE2 bootstrapper supported

kubefire cluster create demo --bootstrapper rke2 --worker-count=1export `kubefire cluster env demo`kubectl get nodes
NAME               STATUS   ROLES         AGE   VERSION
571aa705cb721e74   Ready    etcd,master   13m   v1.19.5+rke2r1
bfc490e4fbddea83   Ready    <none>        13m   v1.19.5+rke2r1
  • K0s bootstrapper supported
kubefire cluster create demo --bootstrapper k0s --worker-count=1export `kubefire cluster env demo`kubectl get nodes
NAME               STATUS   ROLES    AGE   VERSION
175481f742c3888d   Ready    <none>   11m   v1.20.1-k0s1
7077693ac337e509   Ready    <none>   12m   v1.20.1-k0s1

v0.3.3

23 Nov 00:26
Compare
Choose a tag to compare
  • [enhancement] Support k3s correct version parsing #40
  • [enhancement] Update ignite 0.8.0 #39
  • [bug] Always deployed the cluster with latest selected K8s minor version even using a specific old version #38
  • [enhancement] Add RKE bootstrapper #31

Notes

  • Please run kubefire install to update ignite to 0.8.0
kubefire install
...kubefire info
CONTAINERD      IGNITE  CNI     RUNC            CNIPLUGIN                 
v1.4.1          v0.8.0  v0.8.7  1.0.0-rc92      0.4.0/kubefire-cni-bridge   
  • RKE bootstrapper supported
kubefire cluster create demo --bootstrapper rke
...export `kubefire cluster env demo`kubectl get nodes
NAME        STATUS   ROLES                      AGE   VERSION
10.62.0.7   Ready    controlplane,etcd,worker   67s   v1.18.12
  • skuba bootstrapper deprecated and removed

v0.3.2

15 Oct 20:07
Compare
Choose a tag to compare
  • [bug] Unable to create a cluster with continuous K8s release #37

Notes

After updating to this version, the kubeadm bootstrapping issue will be fixed.

kubefire info -b -o yaml
kubeadm: v1.19.3,v1.18.10,v1.17.13
k3s: v1.16.15,v1.17.12,v1.18.9,v1.19.2
skuba: v1.4.1,v1.3.5

...kubectl get nodes
NAME               STATUS   ROLES    AGE   VERSION
e194e867771941f3   Ready    master   56s   v1.19.3

v0.3.1

14 Oct 04:20
Compare
Choose a tag to compare
  • [bug] Can't provision K3s agent node #35
  • [bug] Bug: kubefire install messes with unit files #34
  • [enhancement] Add clean cache command #33
  • [bug] Ubuntu rootfs image from ghcr has no systemd installed #32