Skip to content

Commit 7170f25

Browse files
committed
update
1 parent b6f4f79 commit 7170f25

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

docs/docs/explanations/advanced-configuration.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -412,6 +412,7 @@ Defining a wildcard certificate decreases the amount of Common Name (CN) names y
412412
</Tabs>
413413

414414
### Shared Storage Configuration
415+
415416
:::note
416417
As of Nebari 2024.9.1, alpha support for [Ceph](https://docs.ceph.com/en/latest/) shared file systems as an alternative to NFS is available.
417418
:::
@@ -424,18 +425,20 @@ The initial benefit of using Ceph is increased read/write performance compared t
424425
Do not switch from one storage type to another on an existing Nebari deployment. Any files in the user home directory and conda environments will be lost if you do so! On GCP, all node groups in the cluster will be destroyed and recreated. Only change the storage type prior to the initial deployment.
425426
:::
426427

427-
Storage may be configured in the `nebari-config.yaml` file under the storage section.
428+
Storage is configured in the `nebari-config.yaml` file under the storage section.
428429

429430
```yaml
430431
storage:
431-
type: nfs # efs (default on AWS), cephfs
432+
type: nfs
432433
conda_store: 200Gi
433434
shared_filesystem: 200Gi
434435
```
435436

436-
When using the `cephfs` storage type option, the block storage underlying all Ceph storage will be provisioned through the same Kubernetes storage class. By default, Kubernetes will use the default storage class unless a specific one is provided. For enhanced performance, some cloud providers offer premium storage class options.
437+
Supported storage types are nfs (default on most cloud providers), efs (default on AWS), and cephfs.
438+
439+
When using the `cephfs` storage type option, the block storage underlying all Ceph storage will be provisioned through the same Kubernetes storage class. By default, Kubernetes will use the default storage class unless a specific one is provided. For enhanced performance, some cloud providers offer premium storage class options.
437440

438-
You can specify the desired storage class under `storage.ceph` section in the configuration file. Below are examples of potential storage class values for various cloud providers:
441+
You can specify the desired storage class under `storage.ceph` section in the configuration file. Below are examples of potential storage class values for various cloud providers:
439442

440443
<Tabs>
441444
<TabItem label="AWS" value="AWS" default="true">
@@ -474,6 +477,7 @@ Ceph is not supported on local deployments.
474477
:::note
475478
Premium storage might not be available for certain cloud providers on all node types, which can affect performance and availability. Make sure to check the documentation for your specific cloud provider to confirm premium storage options and their compatibility with your node types.
476479
:::
480+
477481
## More configuration options
478482

479483
Learn to configure more aspects of your Nebari deployment with the following topic guides:

0 commit comments

Comments
 (0)