Vendor in v1.19.0 into master so QA and community testing can begin.
davidnuzik
All 5 comments
Posting here for informative purposes. upstream v1.19.0 k8s is out: https://github.com/kubernetes/sig-release/issues/1196
(As of posting 8/26 2:30pm pacific they have yet to check everything off but is indeed done and publicly announced. They just haven't updated the linked GH issue yet)
davidnuzik
on 26 Aug 2020
We're actively working on this. Approximate timeline is to release k3s 1.19 in two weeks.
We need to update k3s's authentication bootstrapping due to the removal of the --basic-auth-file flag being dropped from Kubernetes (see https://github.com/kubernetes/kubernetes/pull/89069)
cjellick
on 26 Aug 2020
also some existing clusters probably were created with basic-auth-file as the main authn mechanism so that should be migrated to --token-auth-file aswell.
schmitch
on 28 Aug 2020
Upstream v1.19.1 plans to drop 9/9; as such we created https://github.com/rancher/k3s/issues/2217 to bump to this. We plan to push out k3s v1.19.1+k3s1 and skip .0 due to 1) the testing effort required for a new minor release and 2) the short time between .0 and .1 release upstream.
davidnuzik
on 8 Sep 2020
I am closing this issue because we will test v1.19 via https://github.com/rancher/k3s/issues/2217 (v1.19.1) instead.
davidnuzik
on 8 Sep 2020
Related issues
ashrafgt
路
3Comments
wpwoodjr
路
3Comments
weber-software
路
3Comments
joakimr-axis
路
3Comments
ubergeek801
路
3Comments
Most helpful comment
We're actively working on this. Approximate timeline is to release k3s 1.19 in two weeks.
We need to update k3s's authentication bootstrapping due to the removal of the
--basic-auth-fileflag being dropped from Kubernetes (see https://github.com/kubernetes/kubernetes/pull/89069)