Skip to content

Commit 0bb33c7

Browse files
committed
add correct annotations for flux resources app
1 parent a76c9e7 commit 0bb33c7

File tree

1 file changed

+13
-6
lines changed

1 file changed

+13
-6
lines changed

docs/tanzu/tap-gitops/tap-gitops-prep.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -686,12 +686,9 @@ metadata:
686686
name: flux-initial-content-sync
687687
namespace: tanzu-sync
688688
annotations:
689-
kapp.k14s.io/change-group: tanzu-sync
690-
kapp.k14s.io/change-rule.0: "upsert after upserting tanzu-sync-secrets"
691-
kapp.k14s.io/change-rule.1: "upsert after upserting install-registry-export"
692-
#! if registry credentials are deleted before sync-managed software is removed, uninstall can be slow or fail.
693-
kapp.k14s.io/change-rule.2: "delete before deleting tanzu-sync-secrets"
694-
kapp.k14s.io/change-rule.3: "delete before deleting install-registry-export"
689+
kapp.k14s.io/change-group: tanzu-sync-flux
690+
kapp.k14s.io/change-rule.0: "upsert after upserting tanzu-tanzu-sync"
691+
kapp.k14s.io/disable-wait: ""
695692
spec:
696693
serviceAccountName: sync-sa
697694
fetch:
@@ -709,6 +706,16 @@ spec:
709706
- kapp: {}
710707
```
711708

709+
!!! Warning "Disable Wait"
710+
We create resources related to the FluixCD CRDs, the CRDs are yet to be installed when the `tanzu-sync` App runs for the first time.
711+
712+
To avoid having the `tanzu-sync` to error and halt, forgoing the installation of TAP, we instruct to ***not wait*** on our Flux resources _app_. This way, the `tanzu-sync` manages the flux App but doesn't look at its status to reflect its own.
713+
714+
We do this with the KAPP annotation `kapp.k14s.io/disable-wait: ""`.
715+
716+
The `flux-initial-content-sync` App fails to reconcile until TAP installs FluxCD and its CRDs.
717+
It eventually reaches a successfull state.
718+
712719
Our folder now looks like this:
713720

714721
```sh

0 commit comments

Comments
 (0)