Skip to content

Update index.md #160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
noctarius merged 1 commit into from
Jun 18, 2026
Merged

Update index.md #160

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions docs/deployments/deployment-preparation/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,6 @@ weight: 20000
Proper deployment planning is essential for ensuring the performance, scalability, and resilience of a simplyblock
storage cluster.

!!! tip
For OpenShift environments, simplyblock’s **recommended** deployment model is
**hyper-converged**.

## Deployment Models

Two deployment options are supported:
Expand All @@ -21,8 +17,9 @@ Two deployment options are supported:

- **Kubernetes**: In Kubernetes, both **disaggregated** deployments with dedicated workers or clusters for storage
nodes, or **hyper-converged deployments** (co-located with compute workloads) are supported. A wide range of
Kubernetes distros and operating systems are supported. For OpenShift clusters, the hyper-converged deployment model
is recommended. Kubernetes Knowledge is required.
Kubernetes distros and operating systems are supported. There is no essential difference between the two models from a
deployment perspective, if the same cluster is used to serve and consume the storage: it becomes a question of
node tagging only.

## General Information on Requirements

Expand Down
Loading