Skip to content

Commit

Permalink
chore: vale syntax issues
Browse files Browse the repository at this point in the history
Signed-off-by: Piotr Zaniewski <[email protected]>
  • Loading branch information
Piotr1215 committed Oct 2, 2024
1 parent 261fdfb commit 0377cc1
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions platform/understand/externally-vs-platform-deployed.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ These are virtual clusters that are deployed and fully managed through our platf

Platform-managed clusters provide an integrated experience with centralized management and full platform feature utilization.

## Externally-Managed Virtual Clusters
## Externally Managed Virtual Clusters

These virtual clusters are initially deployed outside of our platform, using tools like Helm or custom scripts. While they can be imported into the platform for some level of management, they retain their original ownership and have limited platform integration.

Expand All @@ -50,23 +50,25 @@ In short, the key differences are:
- Update mechanism: Platform-driven vs. externally controlled
:::

📝 Current limitations for externally-managed clusters:
📝 Current limitations for externally managed clusters:
- Sleep mode unavailable
- Pod and audit logging restricted

Feature parity is in active development. Most functionalities are identical across both cluster types.

Choose based on your preferred cluster lifecycle management approach.

## Choosing Between Platform-Managed and Externally-Managed Clusters
## Choosing Between Platform-Managed and Externally Managed Clusters

The choice between platform-managed and externally-managed virtual clusters is not a one-size-fits-all decision. It can be made on a per-project or even per-vcluster basis, allowing for a mix-and-match approach that best suits your specific needs.
The choice between platform-managed and externally managed virtual clusters is not a one-size-fits-all decision. It can be made on a per-project or even per-vcluster basis, allowing for a mix-and-match approach that best suits your specific needs.

Consider the following factors when making your decision:

1. **Existing Infrastructure**: If you already have tools in place for lifecycle management of virtual clusters (e.g., ArgoCD, ClusterAPI), you might prefer externally-managed clusters for those specific projects or vclusters.
1. **Existing Infrastructure**: If you already have tools in place for lifecycle
management of virtual clusters (e.g., ArgoCD, ClusterAPI), you might prefer
externally managed clusters for those specific projects or virtual clusters.
2. **Integration Needs**: For projects requiring tight integration with platform features, platform-managed clusters might be more suitable.
3. **Management Preferences**: Some teams might prefer the centralized management offered by platform-managed clusters, while others might opt for the flexibility of externally-managed clusters.
3. **Management Preferences**: Some teams might prefer the centralized management offered by platform-managed clusters, while others might opt for the flexibility of externally managed clusters.

Remember, you can use both types within the same environment, choosing the most appropriate option for each virtual cluster based on its specific requirements and your team's preferences.

Expand Down

0 comments on commit 0377cc1

Please sign in to comment.