From 398003f477e6a51a73d210ea962cd77def8bf660 Mon Sep 17 00:00:00 2001 From: David Young Date: Mon, 25 Jul 2022 22:40:09 +1200 Subject: [PATCH] Bump flux design title Signed-off-by: David Young --- manuscript/kubernetes/deployment/flux/design.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/manuscript/kubernetes/deployment/flux/design.md b/manuscript/kubernetes/deployment/flux/design.md index 6301cae..e7742b7 100644 --- a/manuscript/kubernetes/deployment/flux/design.md +++ b/manuscript/kubernetes/deployment/flux/design.md @@ -1,14 +1,15 @@ --- -description: Kubernetes Flux deployment strategy - Design +title: Using fluxcd/fluxv2 to deploy from helm with GitOps +description: This page details a deployment design pattern which facilitates the use of fluxcd/fluxv2 to provided a tiered structure of helm releases, so that you can manage your cluster services via GitOps using a single repository. --- -# Design +# Using helm with GitOps via fluxv2/fluxv2 !!! question "Shouldn't a design **precede** installation instructions?" In this case, I felt that an [installation](/kubernetes/deployment/flux/install/) and a practical demonstration upfront, would help readers to understand the flux design, and make it simpler to then explain how to [operate](/kubernetes/deployment/flux/operate/) flux themselves! 💪 Flux is power and flexible enough to fit many use-cases. After some experience and dead-ends, I've worked out a way to deploy Flux with enough flexibility but structure to make it an almost-invisible part of how my cluster "just works" on an ongoing basis.. -## Diagram +## Illustration Consider this entity relationship diagram: @@ -33,7 +34,7 @@ Consider this entity relationship diagram: app-containers }|..|o app-sealed-secrets : references ``` -## Explanation +## Description And here's what it all means, starting from the top...