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
{{ message }}
Repository navigation
Commit 119d582
Browse filesBrowse the repository at this point in the historyBrowse files
### Lower-level tenants can access the cluster services of their parent (provided they do not run their own)
34
+
### Nesting tenants and reusing parent services
35
+
36
+
Tenants can be nested.
37
+
A tenant administrator can create nested tenants using the "Tenant" application from the catalogue.
38
+
39
+
Higher-level tenants can view and manage the applications of all their children tenants.
40
+
If a tenant does not run their own cluster services, it can access ones of its parent.
31
41
32
-
Thus, you can create `tenant-u1` with a set of services like `etcd`, `ingress`, `monitoring`. And create another tenant namespace `tenant-u2` inside of `tenant-u1`.
42
+
For example, you create:
43
+
- Tenant `tenant-u1` with a set of services like `etcd`, `ingress`, `monitoring`.
44
+
- Tenant `tenant-u2` nested in `tenant-u1`.
33
45
34
46
Let's see what will happen when you run Kubernetes and Postgres under `tenant-u2` namespace.
35
47
36
-
Since `tenant-u2` does not have its own cluster services like `etcd`, `ingress`, and `monitoring`, the applications will use the cluster services of the parent tenant.
37
-
This in turn means:
48
+
Since `tenant-u2` does not have its own cluster services like `etcd`, `ingress`, and `monitoring`,
49
+
the applications running in `tenant-u2` will use the cluster services of the parent tenant.
38
50
39
-
- The Kubernetes cluster data will be stored in etcd for `tenant-u1`.
40
-
- Access to the cluster will be through the common ingress of `tenant-u1`.
41
-
- Essentially, all metrics will be collected in the monitoring from `tenant-u1`, and only it will have access to them.
51
+
This in turn means:
42
52
53
+
- The Kubernetes cluster data will be stored in `etcd` for `tenant-u1`.
54
+
- Access to the cluster will be through the common `ingress` of `tenant-u1`.
55
+
- Essentially, all metrics will be collected in the `monitoring` from `tenant-u1`, and only that tenant will have access to them.
0 commit comments