Skip to content

Commit cd508e6

Browse files
committed
docs(platform): document ingress.rootEnabled
The platform now carries whether the root Tenant runs ingress-nginx, and tenant-root's applications read it to decide whether to wait for ingress-nginx and whether to create their Ingress objects. Nothing ties the value to Tenant/root spec.ingress, so operators need to know to set it. Assisted-by: LLM Signed-off-by: Alexey Artamonov <[email protected]>
1 parent bf54529 commit cd508e6

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

‎content/en/docs/next/operations/configuration/platform-package.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,12 @@ gateway:
160160
| --- | --- | --- |
161161
| `scheduling.globalAppTopologySpreadConstraints` | `""` | Global pod topology spread constraints applied to all managed applications. |
162162

163+
#### Ingress
164+
165+
| Value | Default | Description |
166+
| --- | --- | --- |
167+
| `ingress.rootEnabled` | `true` | Whether the root tenant runs its own ingress-nginx, that is, whether `Tenant/root` has `spec.ingress: true`. When `true`, applications in `tenant-root`, and every tenant that inherits its ingress from the root, are told their ingress lives in `tenant-root`: they render `Ingress` objects with the `tenant-root` class, and SeaweedFS in `tenant-root` waits for `ingress-nginx-system` before it starts. When `false`, they are told there is no ingress: SeaweedFS starts without waiting, its S3 `Ingress`, Grafana's `Ingress` and the proxied ingress-nginx addon `Ingress` of a tenant Kubernetes cluster are not created, and the remaining `Ingress` objects are created without a class. Nothing sets `spec.ingress` on the root Tenant from this value: set it to match the root Tenant. With `true` while the root tenant has ingress disabled, SeaweedFS in `tenant-root` waits for an ingress-nginx that never comes up, and so does the platform backup bucket. The default `true` keeps the earlier behaviour. |
168+
163169
#### Monitoring
164170

165171
| Value | Default | Description |

0 commit comments

Comments
 (0)