Kubernetes 1.18

[NikoGrano]

Firstly, Thanks for doing all work for 1.17! I've been following it and trying to learn at same moment how ansible and terraform works.

Anyways, there seems to be K8 1.18 available. Have you been thinking about that?

[rvasilev]

@NikoGrano I'm looking into it

[NikoGrano]

Btw, have you already got the 1.17 working or is it WIP? I'm looking forward for that and I can try put my effort also into it, if you just keep the branch up-to-date always. :)

[rvasilev]

@NikoGrano 1.17 is up and running. You're welcome to test it. The thing is that it'll be used for hetzner hosted homelab at most. Maybe the better way is to use production ready solution (read - kubespray) with hcloud bindings.

Persistent Volume creation should work but was not tested for now.

Readme instructions is missing the main change from original author repository. There are two new variables in env/values.yaml that allow to use existing floating ips.

https://www.github.com/linux-noob/hcloud-k8s/tree/master/env%2Fvalues.yaml.example

use_my_ip = 1 disables new floating ip creation,
my_ip_tag says to the script which available tagged floating ip should be used.

[NikoGrano]

I go for production solution with managed k8 from Google. Before that I need something where I can just test stuff and learn.

Which branch I should use? I was trying to use next-1.17 but it gets stuck in waiting tiller. I will check some things today, but this was case last time I tested while ago.

https://github.com/linux-noob/hcloud-k8s/blob/next-1.17/roles/metal-lb/tasks/main.yaml#L32

[rvasilev]

@NikoGrano b40b49ba2977209377b9734a40db272192762119 was the last non-destructive commit, playbook worked as expected and deployed 1.16 without any problems.

I had no problems test-deploying 1.17 branch.

[NikoGrano]

I will checkout this again later today and report directly back to you! Thanks for you time.