You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: charts/external-secrets/Bootstrapping-Guide.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ In Flux, we can't have dependencies between Flux Kustomization and HelmRelease,
10
10
11
11
Both controllers manage the resources independently, at different moments, with no possibility to wait for each other. This means that we have a wonderful race condition where sometimes the CRs (`SecretStore`,`ClusterSecretStore`...) tries to be deployed before than the CRDs needed to recognize them.
- First when creating the management cluster we will need to create manually a secret for authenticating the SecretStore also we need to create`ClusterResourceSet` for the AWS secret to be able to bootstrap it to leaf cluster. This will be copied for bootstrap location as shown before.
370
368
@@ -433,7 +431,7 @@ For the cluster template we will need to add 2 labels
433
431
434
432
i) `weave.works/flux: bootstrap` to match the booting clusters with the `**ClusterBootstrapConfig`** job
435
433
436
-
ii) `secretmanager: aws` to match the the booting clusters with the `ClusterResourceSet` for the AWS secret
434
+
ii) `secretmanager: aws` to match the the booting clusters with the `ClusterResourceSet` for the AWS secret
0 commit comments