1.3.0

[tkollo]

Hi,

It's not an issue, more a request:
The current master branch is compatible with 1.15.x kubernetes but only 1.2.0 has a release which is only tested up to 1.14.1, could you release a new version here that is compatible with 1.15.7 (we would like to use it on new AKS clusters that use latter version, ideally installed straight from this github), it would be a great help if you could add it.

[onedr0p]

This project seriously needs some loving from the maintainers.

[kwaazaar]

It's becoming hard to use, because current version has vulnerabilities. Not very strange if the images are not rebuild regularly. Tag 'latest' was built 9 months ago: https://hub.docker.com/layers/weaveworks/kured/1.2.0/images/sha256-0d4bf4911f10ef1e3bd088f331e9412cf2d870bec2780d555c4671774503c73c

• Critical: CVE-2019-14697
• High: CVE-2018-20679, CVE-2019-5747

[tkollo]

@kwaazaar

Hm, that's unfortunate, do you know of any other alternative?

[dholbach]

Hello everyone. We will be working on a new release soon. Can we try to disentagle the conversation points a little bit?

So

• Formal release (to include scheduling changes)? #97 is about a new release
• can somebody take a look at Kured v.1.2 fails on Kubernetes v.1.16 (on prem, kubeadm created) #89 regarding the new Kubernetes releases and maybe test it?
• regarding CVEs:
  • CVE-2019-14697 was discussed in Upgrading to latest alpine #100
  • can somebody check which Alpine release fixes the other two CVEs?

Thanks a lot for hanging in there everyone!

[dholbach]

CVE-2018-20679 and CVE-2019-5747 should be fixed since Alpine 3.10.0 as well, which has Busybox 1.30.1.

Closing this issue as duplicate of #97.

[dholbach]

1.3.0 is out now: https://github.com/weaveworks/kured/releases/tag/1.3.0 🎆