Automated management of large-scale applications on Kubernetes (incubating project under CNCF)
To install or upgrade to the old version, see installation doc.
To install or upgrade to the old version, see installation doc.
To install or upgrade to the old version, see installation doc.
No, really, you must read this before you upgrade
Enhanced Operation
Advanced Workload
Sidecar Container
Application Protection
Others
To install or upgrade to the old version, see installation doc.
We start kruise-manger with a non-root user to further enhance the security of kruise-manager. (#1491, @zmberg)
To install or upgrade to the old version, see installation doc.
In version 1.5.1, the focus was on enhancing UnitedDeployment and addressing various bug fixes:
Add the ability to plan the lower and upper bound of capacity to the subsets in UnitedDeployment (#1428, @veophi)
Fix unexpected job recreation by adding controller-revision-hash label for ImageListPullJob. (#1441, @veophi)
Add prometheus metrics for pub and deletion protection to enhance observability for pub & deletion protection (#1398, @zmberg)
Add enable pprof flag for kruise daemon, now you can disable the pprof of kruise daemon (#1416, @chengjoey)
Fix SidecarSet upgrade exception for UpdateExpectations to solve the problem of updating the image of the sidecar container (#1435, @zmberg])
add audit log for pub and deletion protection to enhance observability for pub & deletion protection (#1438, @zmberg])
To install or upgrade to the old version, see installation doc.
No, really, you must read this before you upgrade
updatedAvailableReplicas
field in status. (#1317, nitishchauhan0022)And some bugs were fixed by (#1238, y-ykcir), (#1335, ls-2018), (#1301, wangwu50), (#1395, ywdxz), (#1304, kevin1689-cloud), (#1348, #1343, Colvin-Y), thanks!
To install or upgrade to the old version, see installation doc.
No, really, you must read this before you upgrade
In the Kubernetes world, it is challenging to use long-running sidecar containers for short-term job because there is no straightforward way to terminate the sidecar containers when the main container exits. For instance, when the main container in a Pod finishes its task and exits, it is expected that accompanying sidecars, such as a log collection sidecar, will also exit actively, so the Job Controller can accurately determine the completion status of the Pod. However most sidecar containers lack the ability to discovery the exit of main container.
For this scenario OpenKruise provides the JobSidecarTerminator capability, which can terminate sidecar containers once the main containers exit.
For more detail, please refer to its proposal.