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/platform/guides/account-management/site-administration/client-org.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,9 @@ A Client Organization provides logical separation between different clients shar
21
21
22
22
Before creating a Client Organization, make sure the following are already in place:
23
23
24
-
-**A Hub cluster is set up** — See [Create Hub & Spoke](../../cluster-management/hub-ui/create.md) for the full setup guide.
24
+
-**A Hub cluster is set up** — See [Create Hub & Spoke](../../../cluster-management/hub-ui/create.md) for the full setup guide.
25
25
-**A Spoke cluster is connected to the Hub** — The Spoke must be linked and accepted by the Hub administrator.
26
-
-**The Spoke cluster is licensed** — A valid license certificate must be applied to the Spoke. Without it, database features remain in a **Warning** state and the organization cannot be created. See [License Management](../../cluster-management/hub-ui/license-management.md) for details.
26
+
-**The Spoke cluster is licensed** — A valid license certificate must be applied to the Spoke. Without it, database features remain in a **Warning** state and the organization cannot be created. See [License Management](../../../cluster-management/hub-ui/license-management.md) for details.
27
27
28
28
> ⚠️ Always perform these steps from an **Organization/Work account**. Personal accounts do not support Hub-Spoke features.
Copy file name to clipboardExpand all lines: docs/platform/guides/billing-and-usage-guide/overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ What you’ll see in the Billable table
54
54
- Usage covered by the **30‑day free contract** when there’s no paid contract for the selected product.
55
55
56
56
**How to influence these numbers:**
57
-
- Cluster mode (`PROD` vs `NON‑PROD`) and namespace trials are configured in Cost Management: [Cost Management](./cost-management.md)
57
+
- Cluster mode (`PROD` vs `NON‑PROD`) and namespace trials are configured in Cost Management: [Cost Management](../cost-management.md)
58
58
- Contract behavior (`paid` vs. `30‑day free` when none exists) is described here: [Contract docs](http://appscode.com/docs/en/guides/license-management/contract.html)
59
59
60
60
**For more details, please contact**[AppsCode administrators](https://appscode.com/contact/).
Copy file name to clipboardExpand all lines: docs/platform/guides/client-organization/add-cluster-to-existing-client-organization.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
@@ -12,40 +12,40 @@ section_menu_id: guides
12
12
13
13
# Add a Cluster to an Existing Client Organization
14
14
15
-
You can assign additional clusters to a client organization after it has been created. The **Add Cluster** wizard reuses the same **Gateway Configuration** and **Telemetry Configuration** steps as the [Create Client Organization](./create-client-organization.md) wizard.
15
+
You can assign additional clusters to a client organization after it has been created. The **Add Cluster** wizard reuses the same **Gateway Configuration** and **Telemetry Configuration** steps as the [Create Client Organization](../create-client-organization.md) wizard.
16
16
17
17
## Open the Client Organization
18
18
19
19
Go to **Site Administration → Client Organizations** and click the organization's **Name** in the list to open its details.
20
20
21
-
21
+
22
22
23
23
## Find the Add Cluster option
24
24
25
25
On the organization's details page, the **Clusters** section lists the clusters already assigned to the organization. Click **Add Cluster** in the top-right of that section to start the wizard.
26
26
27
-
27
+
28
28
29
29
## Step 1: Select Cluster
30
30
31
31
In the first step of the **Add Cluster** wizard, choose the cluster to assign and optionally tune where its database workloads are scheduled.
32
32
33
-
33
+
34
34
35
35
-**Hub Cluster***(required)* — the management (hub) cluster for this assignment.
36
36
-**Spoke Cluster***(required)* — the spoke cluster where the organization's databases run.
37
37
-**Configure DB Nodepool***(optional)* — key/value labels used to target specific nodes for database workloads.
38
38
-**Tolerations***(optional)* — add tolerations so workloads can be scheduled onto tainted nodes. Each toleration takes an **Effect**, **Key**, **Operator**, and **Value**.
39
39
40
-
40
+
41
41
42
42
Click **Next** to continue.
43
43
44
44
## Remaining Steps
45
45
46
46
After selecting the cluster, the wizard continues with the same **Gateway Configuration** and **Telemetry Configuration** steps used when creating a client organization:
47
47
48
-
-[Gateway Configuration](./create-client-organization.md#step-3-gateway-configuration) — choose a shared or dedicated gateway.
49
-
-[Telemetry Configuration](./create-client-organization.md#step-4-telemetry-configuration) — configure log and metrics retention.
48
+
-[Gateway Configuration](../create-client-organization.md#step-3-gateway-configuration) — choose a shared or dedicated gateway.
49
+
-[Telemetry Configuration](../create-client-organization.md#step-4-telemetry-configuration) — configure log and metrics retention.
50
50
51
51
Configure them as needed, then finish to add the cluster to the organization. The new cluster then appears in the **Clusters** section of the organization's details page.
Copy file name to clipboardExpand all lines: docs/platform/guides/client-organization/create-client-organization.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ The wizard has four steps, shown on the right side of the form:
25
25
26
26
Enter the organization details and choose its administrator.
27
27
28
-
28
+
29
29
30
30
-**Organization Name***(required)* — used to provision the three namespaces (`orgName`, `orgName-gw`, and `orgName-monitoring`).
31
31
-**Organization Display Name** — a friendly name shown in the UI.
@@ -42,7 +42,7 @@ Click **Next** to continue.
42
42
43
43
Assign the organization to a hub and spoke cluster, and optionally tune where its database workloads are scheduled.
44
44
45
-
45
+
46
46
47
47
-**Hub Cluster***(required)* — the management (hub) cluster for this organization.
48
48
-**Spoke Cluster***(required)* — the spoke cluster where the organization's databases run.
@@ -59,39 +59,39 @@ Choose how the organization exposes its workloads. There are two top-level optio
59
59
60
60
Select **Use Shared Gateway** to reuse the platform's shared gateway. No additional gateway configuration is required.
61
61
62
-
62
+
63
63
64
64
### Use Dedicated Gateway
65
65
66
66
Select **Use Dedicated Gateway** to give the organization its own gateway. Then pick a **Dedicated Gateway Type**.
67
67
68
-
68
+
69
69
70
70
#### Use Existing Gateway
71
71
72
72
Choose **Use Existing Gateway** and select a **Gateway Preset Config** to reuse an already-defined gateway configuration.
73
73
74
-
74
+
75
75
76
76
#### Use Custom Gateway
77
77
78
78
Choose **Use Custom Gateway** to define the gateway yourself. Use **Can it be used as a shared Gateway?** to pick a starting point.
79
79
80
80
**Preload From Existing One** — start from an existing **Gateway Preset Config**, then edit the pre-filled fields across the **In Cluster** (certificates and keys), **Envoy Service** (service type, external IP, traffic policy, ports, provisioner type), and **Infra** (DNS provider, host type, host/domain, TLS issuer) sections.
81
81
82
-
82
+
83
83
84
84
**Create New From Start** — build the gateway from scratch by filling in the same **In Cluster**, **Envoy Service**, and **Infra** sections with your own values.
85
85
86
-
86
+
87
87
88
88
Click **Next** to continue.
89
89
90
90
## Step 4: Telemetry Configuration
91
91
92
92
In the final step, configure the telemetry settings that will be applied to the organization's `orgName-monitoring` namespace, then finish to create the client organization.
93
93
94
-
94
+
95
95
96
96
-**Select Monitoring Type** — choose the monitoring stack to provision for the organization.
97
97
-**Logs** — set the **Retention Period** for collected logs.
@@ -106,4 +106,4 @@ Once created, the organization appears in the **Client Organizations** list and
106
106
107
107
## Next steps
108
108
109
-
-[Add a Cluster to an Existing Client Organization](./add-cluster-to-existing-client-organization.md) — assign additional clusters after the organization is created.
109
+
-[Add a Cluster to an Existing Client Organization](../add-cluster-to-existing-client-organization.md) — assign additional clusters after the organization is created.
Copy file name to clipboardExpand all lines: docs/platform/guides/client-organization/overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,5 +35,5 @@ Client organizations are managed from **Site Administration → Client Organizat
35
35
36
36
## Next steps
37
37
38
-
-[Create a Client Organization](./create-client-organization.md) — a step-by-step walkthrough of the creation wizard.
39
-
-[Add a Cluster to an Existing Client Organization](./add-cluster-to-existing-client-organization.md) — assign additional clusters after the organization is created.
38
+
-[Create a Client Organization](../create-client-organization.md) — a step-by-step walkthrough of the creation wizard.
39
+
-[Add a Cluster to an Existing Client Organization](../add-cluster-to-existing-client-organization.md) — assign additional clusters after the organization is created.
Copy file name to clipboardExpand all lines: docs/platform/guides/cluster-management/add-cluster/import-rancher-cluster.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,11 +17,11 @@ Importing a `Rancher-Managed` cluster requires a Rancher Type Credential and a R
17
17
18
18
## Create Rancher Type Credential
19
19
20
-
Add a credential of type "Rancher" — see [Credentials Management](../../account-management/kubernetes/credentials.md#rancher).
20
+
Add a credential of type "Rancher" — see [Credentials Management](../../../account-management/kubernetes/credentials.md#rancher).
21
21
22
22
## Create a Rancher Managed Organization
23
23
24
-
Rancher clusters belong to Rancher Managed organizations, not personal accounts. Follow [Create a New Organization](../../account-management/orgs-members.md#create-a-new-organization) with these settings:
24
+
Rancher clusters belong to Rancher Managed organizations, not personal accounts. Follow [Create a New Organization](../../../account-management/orgs-members.md#create-a-new-organization) with these settings:
25
25
26
26
1. Set the organization's Origin to `Rancher Managed`.
27
27
2. Provide the Rancher `API Endpoint` (found on the `Account & API Keys` page).
@@ -30,4 +30,4 @@ Rancher clusters belong to Rancher Managed organizations, not personal accounts.
30
30
## Import the Cluster
31
31
32
32
1. Switch to the Rancher organization: in the [AppsCode Console](https://console.appscode.com), click your profile, choose `Switch Account`, and select the Rancher organization.
33
-
2. Follow the standard import process in [Import Vendor Managed Clusters](import-vendor-managed.md).
33
+
2. Follow the standard import process in [Import Vendor Managed Clusters](../import-vendor-managed.md).
0 commit comments