update readme and advanced-usage doc

This commit is contained in:
jpgouin
2025-03-03 13:21:07 +00:00
parent a3cbe42782
commit 07b9cdcc86
2 changed files with 36 additions and 1 deletions
+33 -1
View File
@@ -6,7 +6,7 @@ This document provides advanced usage information for k3k, including detailed us
The `Cluster` resource provides a variety of fields for customizing the behavior of your virtual clusters. You can check the [CRD documentation](./crds/crd-docs.md) for the full specs.
**Note:** Most of these customization options can also be configured using the `k3kcli` tool. Refer to the `k3kcli` documentation for more details.
**Note:** Most of these customization options can also be configured using the `k3kcli` tool. Refer to the [k3kcli](./cli/cli-docs.md) documentation for more details.
@@ -112,3 +112,35 @@ The `clusterDNS` field specifies the IP address for the CoreDNS service. It need
### `serverArgs`
The `serverArgs` field allows you to specify additional arguments to be passed to the K3s server pods.
## Using the cli
You can check the [k3kcli documentation](./cli/cli-docs.md) for the full specs.
### Examples for no storage provider:
* Ephemeral Storage:
```bash
k3kcli cluster create my-cluster --persistence-type ephemeral
```
* Static Storage (Requires pre-provisioned PVs):
```bash
k3kcli cluster create my-cluster --persistence-type static
```
(You will need to ensure that persistent volumes that match the requirements of your k3k cluster exist before creation)
*Important Notes:*
* When using `--persistence-type static`, you must manually create PersistentVolumes (PVs) that match the storage requirements of your K3K cluster.
* Using `--persistence-type ephemeral` will result in data loss if the nodes are restarted.
* It is highly recommended to use `--persistence-type dynamic` with a configured storage class.