Skip to content

Commit f4d511f

Browse files
djwfyiclaude
andcommitted
docs(doc-1410): fix vale warnings in platform/administer/ batch 1
- Remove "Please" from quotas.mdx admonition (Loft.exclude-please) - Remove backticks from VirtualClusterTemplate, AppTemplate, SpaceTemplate in prose and table in templates/overview.mdx (Loft.kubernetes-api-kinds) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 5dcaaad commit f4d511f

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

platform/administer/projects/quotas.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Quotas allow you to set resource usage and count limits for the project. This wo
1818
defined across the whole project or on a per-user/per-team basis.
1919

2020
:::info Project quotas with multiple tenant clusters
21-
Please be aware that when you create multiple tenant cluster instances, the individually used resources count toward the shared project quota.
21+
When you create multiple tenant cluster instances, the individually used resources count toward the shared project quota.
2222
:::
2323

2424
## Quotas on Active Resources

platform/administer/templates/overview.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import NavStep from "@site/src/components/NavStep";
1414

1515
# Templates overview
1616

17-
Templates define reusable configurations for creating tenant clusters, applications, and namespaces. They allow platform teams to standardize resource provisioning while giving users a controlled way to customize certain settings. Templates are implemented using Kubernetes custom resources (`VirtualClusterTemplate`, `AppTemplate`, and `SpaceTemplate`) and can be managed with tools such as `kubectl`, Helm, or ArgoCD.
17+
Templates define reusable configurations for creating tenant clusters, applications, and namespaces. They allow platform teams to standardize resource provisioning while giving users a controlled way to customize certain settings. Templates are implemented using Kubernetes custom resources (VirtualClusterTemplate, AppTemplate, and SpaceTemplate) and can be managed with tools such as `kubectl`, Helm, or ArgoCD.
1818

1919
Each template type serves a specific purpose. Tenant cluster templates define the base configuration for tenant clusters, including the Kubernetes version, control plane, networking, storage settings, and sync behavior. App templates provide reusable application configurations using Helm charts or Kubernetes manifests. Namespace templates predefine configurations for new namespaces, including role-based access control, resource quotas, and labels.
2020

@@ -33,9 +33,9 @@ vCluster Platform includes templates for tenant clusters, applications, and name
3333

3434
| Template type | Custom resource | Purpose | Common Use Cases |
3535
| ---------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
36-
| Tenant cluster | `VirtualClusterTemplate` | Specifies how tenant clusters are provisioned, including control plane settings, synchronization behavior, and metadata. | Provision tenant clusters with consistent architecture, features, and default settings. |
37-
| App | `AppTemplate` | Defines reusable application configurations, such as Helm charts or Kubernetes manifests . | Deploy standard applications across projects or spaces using consistent settings. |
38-
| Namespace | `SpaceTemplate` | Predefines configurations for new namespaces, including role-based access control, resource quotas, and labels. | Automatically apply baseline policies when a namespace is created. |
36+
| Tenant cluster | VirtualClusterTemplate | Specifies how tenant clusters are provisioned, including control plane settings, synchronization behavior, and metadata. | Provision tenant clusters with consistent architecture, features, and default settings. |
37+
| App | AppTemplate | Defines reusable application configurations, such as Helm charts or Kubernetes manifests . | Deploy standard applications across projects or spaces using consistent settings. |
38+
| Namespace | SpaceTemplate | Predefines configurations for new namespaces, including role-based access control, resource quotas, and labels. | Automatically apply baseline policies when a namespace is created. |
3939

4040
<br />
4141

0 commit comments

Comments
 (0)