ways to rollback: 1. You can simply point your cluster to a previous Git hash and let your GitOps tool sync that hash. This is the fastest way to rollback, but by definition leaves your cluster in intervention. 3. You can have a combination where the GitOps tool itself both syncs a previous Git hash to the cluster and auto-commits (or reverts) to the git repo in order to keep the consistency. are only useful to developers and operators. Business stakeholders have no interest in which Git hash is now deployed at the cluster. Therefore, while GitOps is great for observability on a technical

Containers Runtime Applications Functions Physical Machine Customer Vender Virtual Machine Hardware Virtualization O/S Containers Runtime Applications Functions Container Hardware Virtualization Virtualization O/S Containers Runtime Applications Functions Serverless Hardware Virtualization O/S Containers Runtime Applications Functions ❑ 云计算：去基础架构的过程 ❑ Serverless 符合云计算发展的方向 聚焦业务，快速迭代，提高产品竞争力

actual system state and attempt to apply the desired state. This principle directly mirrors the functions of the Kubernetes controllers, but GitOps applies it to a whole application or infrastructure stack environment to help people on their Gi- tOps adoption journey. Flux performs many of the same functions as Argo CD, but it is different in a lot of ways. The main difference is that Flux uses the Helm modeled after what Weaveworks felt that it meant to do a GitOps workflow. With Flux version 2, the functions were broken up into individual components, called the GitOps Toolkit, and were based on controllers