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: docs/content/guides/kamaji-gitops-flux.md
+28-3Lines changed: 28 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,18 +38,32 @@ Given that Flux it's installed in the *admin cluster* - guide [here](https://flu
38
38
For example, it might be needed to ensure [cert-manager](https://cert-manager.io/) is installed into a *tenant1* cluster with Helm. It can be done by declaring an `HelmRelease` as follows:
39
39
40
40
```yaml
41
+
---
42
+
apiVersion: source.toolkit.fluxcd.io/v1beta2
43
+
kind: HelmRepository
44
+
metadata:
45
+
name: jetstack
46
+
namespace: flux-system
47
+
spec:
48
+
interval: 1m
49
+
url: https://charts.jetstack.io
50
+
---
41
51
apiVersion: helm.toolkit.fluxcd.io/v2beta1
42
52
kind: HelmRelease
43
53
metadata:
44
54
name: tenant1-cert-manager
45
55
namespace: tenants
46
56
spec:
47
57
interval: 5m
58
+
kubeConfig:
59
+
secretRef:
60
+
name: tenant1-admin-kubeconfig
61
+
key: admin.conf
62
+
targetNamespace: default
48
63
chart:
49
64
spec:
50
-
kubeConfig: tenant1-admin-kubeconfig
51
-
chart: jetstack/cert-manager
52
-
version: '4.0.x'
65
+
chart: cert-manager
66
+
version: v1.10.1
53
67
sourceRef:
54
68
kind: HelmRepository
55
69
name: jetstack
@@ -61,6 +75,17 @@ spec:
61
75
62
76
and applying it in the *admin cluster*, alongside the related *jetstack* `HelmRepository`, in the *tenants* `Namespace`.
63
77
78
+
The result would be having Cert Manager installed in the *default* `Namespace` of the tenant *tenant1*'s cluster:
0 commit comments