知识卡片

结构图卡 · 529.d.2

持续协调定义GitOps

理解等级:中级

GitOps 要求期望状态以声明表达、保存不可变版本和完整历史、由代理自动拉取,并持续对照真实状态协调。它不只是新提交触发一次部署:即使代码没变,运行状态偏离时也会恢复。持续协调使版本存储同时成为运行状态的控制依据。

结构图:

flowchart LR
 A[版本化不可变声明] --> B[代理自动拉取]
 B --> C[对照实际状态]
 C --> D[应用差异]
 D --> C
这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 部署基础设施 · 查看原书依据

      The GitOps principles are as follows: Declarative A system managed by GitOps must have its desired state expressed declaratively. Versioned and immutable Desired state is stored in a way that enforces immutability and retains a complete version history. Pulled automatically Software agents automatically pull the

    参考来源

    - 位置:《Infrastructure As Code》第19章《部署基础设施》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch19.html) - 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“GitOps 要求期望状态以声明表达、保存不可变版本和完整历史、由代理自动拉取,并持续对照真实状态协调”这一核心结论;正文的用途与边界据同小节后续论述整理。 - 原始内容:The GitOps principles are as follows: Declarative A system managed by GitOps must have its desired state expressed declaratively. Versioned and immutable Desired state is stored in a way that enforces immutability and retains a complete version history. Pulled automatically Software agents automatically pull the