There were new releases this weekend to fix breaking Hyperkube (more below). Note that Hyperkube is deprecated and will not be built by the Kubernetes project for 1.19, so if you’re the community images for your builds, you need to come up with another plan.
Per last week’s LWKD update, the image repository move was rolled back and will need to be retried later.
Next Deadline: Docs complete July 6, Code Freeze July 9
Hopefully you’re finishing your docs now, so USians can take the holiday weekend off.
1.18.5, 1.17.8, and 1.16.12 were released June 26 to fix multiple kube-proxy failures in Hyperkube. If you don’t use Hyperkube and already installed the prior bugfix release, you don’t need to care. If you do use Hyperkube, skip last week’s patch release and go straight to this one (but be prepared to take on your own Hyperkube maintenance pretty soon)
--kernel-memcg-notificationmoves to the kubelet config file
Last Week In Kubernetes Development (LWKD) is a product of some members of the Kubernetes project, but is not an official publication of the Kubernetes project or the CNCF. All original content is licensed Creative Commons Share-Alike, although linked content and images may be differently licensed. LWKD does collect some information on readers, see our privacy notice for details.
You may contribute to LWKD by submitting pull requests or issues on the LWKD github repo.