From ff2d6fffa63e2e0a4551a9456217f93561351ae3 Mon Sep 17 00:00:00 2001 From: Graeme Hay Date: Tue, 12 Oct 2021 15:32:56 -0700 Subject: [PATCH 1/4] Update PRINCIPLES.md --- PRINCIPLES.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/PRINCIPLES.md b/PRINCIPLES.md index da5b87e..0233f7a 100644 --- a/PRINCIPLES.md +++ b/PRINCIPLES.md @@ -21,3 +21,6 @@ The [desired state](./GLOSSARY.md#desired-state) of a GitOps managed system must Software agents [continuously](./GLOSSARY.md#continuous) observe actual system state and [attempt to apply](./GLOSSARY.md#reconciliation) the desired state. +5. **Manageable "always"** + + Desired state is able to be updated according to users' SLA expectations to update system state, even if the "source" is unavailable. From 3f3b575b1a6cb3a3e3d5c141e2725d72e5708dd9 Mon Sep 17 00:00:00 2001 From: Graeme Hay Date: Tue, 12 Oct 2021 15:34:19 -0700 Subject: [PATCH 2/4] Update GLOSSARY.md --- GLOSSARY.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/GLOSSARY.md b/GLOSSARY.md index 53ab9da..f18b845 100644 --- a/GLOSSARY.md +++ b/GLOSSARY.md @@ -40,7 +40,14 @@ This glossary accompanies the [GitOps Principles](./PRINCIPLES.md), and other su Git, from which GitOps derives its name, is the canonical example used as this state store but any other system that meets these criteria may be used. In all cases, these state stores must be properly configured and precautions must be taken to comply with requirements set out in the GitOps Principles. +- ## Intermediate State Store + A system for storing a copy of the declarations that are mastered in the State Store. This system's purpose is intended to bridge the gap in availability between that of the State Store and the expected availability to make configuration changes to the Software System. The Intermediate State Store will offer an availability the same as or near enough to that of the users' expectations to update configuration in the Software System. + +Where an Intermediate State Store is used, Reconciliation is used between the State Store and the Intermediate State Store and then again between the Intermediate State Store and the Software System.![image](https://user-images.githubusercontent.com/7180729/137037872-934eba46-31a5-4509-a6cd-78aaf5bcbc63.png) + - ## Feedback Open GitOps follows [control-theory](https://en.wikipedia.org/wiki/Control_theory) and operates in a closed-loop. In control theory, feedback represents how previous attempts to apply a desired state have affected the actual state. For example if the desired state requires more resources than exist in a system, the software agent may make attempts to add resources, to automatically rollback to a previous version, or to send alerts to human operators. +- ## Break the Glass +The process of editing the Intermediate State Store directly in the event that a configuration update needs to be made to the Software System but the State Store is unavailable. From 1181a09c69595aeb14668e09f14bf3688620a115 Mon Sep 17 00:00:00 2001 From: Graeme Hay Date: Tue, 12 Oct 2021 15:34:49 -0700 Subject: [PATCH 3/4] Update GLOSSARY.md --- GLOSSARY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GLOSSARY.md b/GLOSSARY.md index f18b845..5cc9a37 100644 --- a/GLOSSARY.md +++ b/GLOSSARY.md @@ -43,7 +43,7 @@ This glossary accompanies the [GitOps Principles](./PRINCIPLES.md), and other su - ## Intermediate State Store A system for storing a copy of the declarations that are mastered in the State Store. This system's purpose is intended to bridge the gap in availability between that of the State Store and the expected availability to make configuration changes to the Software System. The Intermediate State Store will offer an availability the same as or near enough to that of the users' expectations to update configuration in the Software System. -Where an Intermediate State Store is used, Reconciliation is used between the State Store and the Intermediate State Store and then again between the Intermediate State Store and the Software System.![image](https://user-images.githubusercontent.com/7180729/137037872-934eba46-31a5-4509-a6cd-78aaf5bcbc63.png) +Where an Intermediate State Store is used, Reconciliation is used between the State Store and the Intermediate State Store and then again between the Intermediate State Store and the Software System. - ## Feedback From a6b12ea4eb40be16d9e6b3634ee33d1a917f67a6 Mon Sep 17 00:00:00 2001 From: Graeme Hay Date: Tue, 12 Oct 2021 15:35:10 -0700 Subject: [PATCH 4/4] Update GLOSSARY.md --- GLOSSARY.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/GLOSSARY.md b/GLOSSARY.md index 5cc9a37..c8d9451 100644 --- a/GLOSSARY.md +++ b/GLOSSARY.md @@ -42,8 +42,7 @@ This glossary accompanies the [GitOps Principles](./PRINCIPLES.md), and other su - ## Intermediate State Store A system for storing a copy of the declarations that are mastered in the State Store. This system's purpose is intended to bridge the gap in availability between that of the State Store and the expected availability to make configuration changes to the Software System. The Intermediate State Store will offer an availability the same as or near enough to that of the users' expectations to update configuration in the Software System. - -Where an Intermediate State Store is used, Reconciliation is used between the State Store and the Intermediate State Store and then again between the Intermediate State Store and the Software System. + Where an Intermediate State Store is used, Reconciliation is used between the State Store and the Intermediate State Store and then again between the Intermediate State Store and the Software System. - ## Feedback