From a9a73301dd0eaaa74b54843180a49816569a2b78 Mon Sep 17 00:00:00 2001 From: Stefan Prodan Date: Thu, 9 Apr 2020 13:30:22 +0300 Subject: [PATCH] Fix typos Co-Authored-By: Michael Bridgen --- docs/spec/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/spec/README.md b/docs/spec/README.md index d8979524..9024044a 100644 --- a/docs/spec/README.md +++ b/docs/spec/README.md @@ -17,7 +17,7 @@ private HTTPS servers. Each Flux or Helm Operator instance maintains its own Git repository mirror even if all of them point to the same source. If the Git repository host becomes unavailable, the cluster state will diverge from the last -know desired state since the operators will stop the reconciliation due to pull errors. +known desired state since the operators will stop the reconciliation due to pull errors. Decoupling the Kubernetes objects acquisition from the reconciliation process with an in-cluster source manager would make Flux and Helm Operator resilient to outbound connectivity issues and would @@ -25,7 +25,7 @@ simplify the state machine(s) that these controllers operate. Managing the source operations in a dedicated controller could enable Flux to compose the desire state of a cluster from multiple source. -Further more the manifests transformation process could be performed by 3rd party tools +Furthermore, the manifests transformation process could be performed by 3rd party tools (e.g. kustomize, jk, tanka, cue run by Tekton pipelines or Kubernetes Jobs) that subscribe to source changes events.