Skip to content

Releases: ReSearchITEng/kubeadm-playbook

v1.18

22 May 15:24
bbf955c
Compare
Choose a tag to compare
v1.18 Pre-release
Pre-release

v1.18

v1.18.2

11 May 11:31
Compare
Choose a tag to compare
v1.18.2 Pre-release
Pre-release

v1.18.2

v1.17.5

30 Apr 18:52
f529cd7
Compare
Choose a tag to compare

v1.17.5

v1.17.5.dash1

30 Apr 11:48
65210ce
Compare
Choose a tag to compare
v1.17.5.dash1 Pre-release
Pre-release

v1.17.5 - with old dashboard (1)

v1.16.3

27 Nov 22:49
1bad88a
Compare
Choose a tag to compare

bump k8s vers.
small bug fixes.

v1.16.2

26 Nov 22:39
519d9d2
Compare
Choose a tag to compare

major points: fixes for newer debian based systems (kernel 5.3, where some kernel modules are not usable)

v1.16

30 Oct 22:03
ede1bf5
Compare
Choose a tag to compare

v1.16 updates

v1.15.2

07 Aug 20:55
2440e58
Compare
Choose a tag to compare

keepalived can be in docker (OS package is kept also as an option)

v1.15

25 Jun 14:32
1340791
Compare
Choose a tag to compare

multi master fully from kubeadm.
No more need for manual etcd setup.

v1.14

11 May 12:57
082ee50
Compare
Choose a tag to compare

Multimaster is now done using kubeadm's native multimaster solution (custom code has been finally removed).
vsphere setups has been worked:

  • vcenter password is now in a secret
  • cloud-config file is now limited to masters (not required on the nodes)
  • the vsphere_bug_fix script has been improved to do also node delete for fixing vsphere related issues (if any)

cons of 1.14:

  • in 1.14, when multimaster setup is required, kubeadm join for masters is done using command, not config.yaml, therefore, should you have any advanced setting in JoinConfiguration.yml, it will be ignored. (If you don't know what is this about, most probably you are not affected even in multimaster configuration).
  • starting 1.14, we won't support different vms for etcd and others for masters (kubeadm limitation). It's was not a common setup anyway.