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: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,17 +17,17 @@
17
17
</p>
18
18
19
19
If you are using [vcluster](https://www.vcluster.com/) and [ArgoCD](https://argoproj.github.io/argo-cd/), stop reading and jump to [installing](#installing)!
20
-
Why? You have probably noticed that ArgoCD does not detect vcluster-spawned clusters out-of-the-box requiring painful manual/automated ad-hoc registration.
21
-
I have got you covered. This exporter bridges this gap and allows vCluster clusters to be automatically registered in ArgoCD!
20
+
Why? You have probably noticed that ArgoCD does not detect vcluster-spawned clusters out-of-the-box requiring somewhat painful manual/automated ad-hoc registration.
21
+
I have got you covered. This exporter bridges the gap and allows vCluster clusters to be automatically registered in ArgoCD!
22
22
23
23
---
24
24
25
25
## Installing
26
26
27
27
### Helm `dependency`
28
28
> [!TIP]
29
-
> This is particularly useful when you are installing `vcluster` through Helm as well as you can chain the dependencies.
30
-
> Don't forget to add the ArgoCD specific `PostSync` hook annotation to ensure that the exporter runs **after** the `vcluster` is installed.
29
+
> This is particularly useful when you are already installing `vcluster` through Helm as you can correctly sequence the installation of the exporter.
30
+
> Add the ArgoCD specific `PostSync` hook annotation to ensure that the exporter runs **after** the `vcluster` is installed.
0 commit comments