Skip to content

Commit 7288874

Browse files
authored
Merge branch 'main' into docs/fix-broken-refs
2 parents 67bd7af + f1c640d commit 7288874

1 file changed

Lines changed: 45 additions & 0 deletions

File tree

‎content/en/docs/v1.2/guides/tenants/_index.md‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,51 @@ See [Tenant `isolated` flag removed]({{% ref "/docs/v1.2/operations/upgrades#ten
7575
in the upgrade notes for a full worked example.
7676

7777

78+
### Customizing Tenant Services
79+
80+
The tenant flags `etcd`, `monitoring`, `ingress`, and `seaweedfs` install a
81+
*default* configuration of each service. After the service is running, you
82+
can change its spec — add storage pools, tune resource quotas, switch a
83+
SeaweedFS topology to `MultiZone`, etc. — by editing the underlying
84+
application CR. Those manual edits are **not** overwritten when the parent
85+
`Tenant` reconciles.
86+
87+
The workflow has two steps:
88+
89+
1. Turn on the flag on the tenant (checkbox in the Dashboard, or `etcd: true` /
90+
`seaweedfs: true` / ... under `spec.values` in the Tenant `HelmRelease`
91+
manifest you apply with `kubectl`). Cozystack creates the matching
92+
application CR with defaults.
93+
2. Edit the application CR in place. For example, to add a pool to the
94+
tenant-root SeaweedFS instance:
95+
96+
```bash
97+
kubectl edit -n tenant-root seaweedfses.apps.cozystack.io seaweedfs
98+
```
99+
100+
Or patch it non-interactively:
101+
102+
```bash
103+
kubectl patch -n tenant-root seaweedfses.apps.cozystack.io seaweedfs \
104+
--type=merge -p '{"spec":{"volume":{"pools":{"ssd":{"diskType":"ssd","size":"50Gi"}}}}}'
105+
```
106+
107+
The same pattern applies to every tenant-level application CR: `etcd`,
108+
`monitoring`, `ingress`, `seaweedfs`. See
109+
[SeaweedFS storage pools]({{% ref "/docs/v1.2/operations/services/object-storage/storage-pools" %}})
110+
for a worked example that walks the full flow — enabling SeaweedFS on the
111+
tenant and then customizing the resulting CR.
112+
113+
{{% alert color="warning" %}}
114+
Do not try to preconfigure a tenant-level service by applying its CR manifest
115+
*before* the tenant is created — you will hit "namespace not found". And
116+
editing the `Tenant` resource itself to nest service-specific fields (like
117+
SeaweedFS `pools`) under the `Tenant` spec does not work either: tenant-level
118+
flags are booleans, the per-service spec is a separate resource. Enable the
119+
flag first, edit the downstream CR second.
120+
{{% /alert %}}
121+
122+
78123
### Unique Domain Names
79124

80125
Each tenant has its own domain.

0 commit comments

Comments
 (0)