KubeCon + CloudNativeCon + Open Source Summit + AI_dev China 2024

Inplace-update is a controversial technique that is considered bad practice by many cloud native fans. Nevertheless , Inplace-update is used by many practitioners to containerize stateful apps and to greatly speed up rolling progress of stateless apps. In recent versions of k8s, additional support of Inplace-update had emerges, e.g. volume resizing and vertical pod scaling. It is a pity that these features are not integrated with in-tree workload. OpenKruise integrates inplace-update as one of core features of advance workload, and have accumulated many real use cases. We will share the challenges to implement inplace update in k8s such as enhancing pod lifecycle hooks and support inplace-update triggered by metadata changes. In addition, we will share the in-progress effort to integrate recent k8s enhancement into kruise workload so as to enable more cases for inplace update. Finally, we will discuss about the possibility to bring inplace-update feature in in-tree

Inplace-update 是一种备受争议的技术，被许多云原生爱好者认为是不良实践。然而，许多从业者仍然使用 Inplace-update 来容器化有状态应用程序，并大大加快无状态应用程序的滚动进展。在最近的 k8s 版本中，出现了对 Inplace-update 的额外支持，例如卷调整大小和垂直 Pod 缩放。遗憾的是，这些功能尚未与 in-tree 工作负载集成。 OpenKruise 将 Inplace-update 集成为高级工作负载的核心功能之一，并积累了许多真实用例。我们将分享在 k8s 中实现 Inplace-update 的挑战，例如增强 Pod 生命周期钩子和支持通过元数据更改触发 Inplace-update。此外，我们将分享将最近的 k8s 增强集成到 Kruise 工作负载中的正在进行的努力，以便为 Inplace-update 启用更多案例。最后，我们将讨论将 Inplace-update 功能引入 in-tree 工作负载的可能性。