Skip to content
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.

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

fix: helm inconsistency #816

Merged
merged 1 commit into from
Sep 1, 2023
Merged
Changes from all commits
Commits
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
26 changes: 13 additions & 13 deletions content/docs/cosidriver/installation/helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,19 +44,19 @@ Installing any of the CSI Driver components using Helm requires a few utilities

{{<table "table table-striped table-bordered table-sm">}}
| Parameter | Description | Required | Default |
|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------:|--------------------------------------------------------------------------------|
| provisioner.logLevel | The logging level for the COSI driver provisioner. | yes | `"yes"` |
| provisioner.logFormat | The logging format for the COSI driver provisioner. | yes | `"text"` |
| provisioner.image.reposiotry | COSI driver provisioner container image repository. | yes | `"docker.io/dell/cosi"` |
| provisioner.image.tag | COSI driver provisioner container image tag. | yes | `"v0.1.0"` |
| provisioner.image.pullPolicy | COSI driver provisioner container image pull policy. Maps 1-to-1 with [Kubernetes image pull policy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy). | yes | `"IfNotPresent"` |
| sidecar.verbosity | The logging verbosity for the COSI driver sidecar, higher values are more verbose, possible values are integers from _-2,147,483,648_ to _2,147,483,647_. Generally the range used is between -4 and 12. However, there may be cases where numbers outside that range might provide more information. For additional information, refer to the [COSI sidecar documentation](https://github.com/kubernetes-sigs/container-object-storage-interface-provisioner-sidecar). | yes | `5` |
| sidecar.image.reposiotry | COSI driver sidecar container image repository. | yes | `"gcr.io/k8s-staging-sig-storage/objectstorage-sidecar/objectstorage-sidecar"` |
| sidecar.image.tag | COSI driver sidecar container image tag. | yes | `"v20230130-v0.1.0-24-gc0cf995"` |
| sidecar.image.pullPolicy | COSI driver sidecar container image pull policy. Maps 1-to-1 with [Kubernetes image pull policy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy). | yes | `"IfNotPresent"` |
| configuration.create | Specifies whether a secret with driver configuration should be created If set to false, you must set `configuration.secretName` field to an existing configuration secret name. | yes | `true` |
| configuration.secretName | Name can be used to specify an existing secret name to use for the driver configuration or override the generated name (default `cosi-driver`). | | |
| configuration.data | Data should be provided when installing chart, it will be used to create the Secret with the driver configuration. `configuration.create` must be set to `true` for this to work. | no | `""` |
|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------:|--------------------------------------------------------------------------------|
| provisioner.logLevel | The logging level for the COSI driver provisioner. | yes | `4` |
| provisioner.logFormat | The logging format for the COSI driver provisioner. | yes | `"text"` |
| provisioner.image.reposiotry | COSI driver provisioner container image repository. | yes | `"docker.io/dell/cosi"` |
| provisioner.image.tag | COSI driver provisioner container image tag. | yes | `"v0.1.0"` |
| provisioner.image.pullPolicy | COSI driver provisioner container image pull policy. Maps 1-to-1 with [Kubernetes image pull policy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy). | yes | `"IfNotPresent"` |
| sidecar.verbosity | The logging verbosity for the COSI driver sidecar, higher values are more verbose, possible values are integers from _-2,147,483,648_ to _2,147,483,647_. Generally the range used is between -4 and 12. However, there may be cases where numbers outside that range might provide more information. For additional information, refer to the [COSI sidecar documentation](https://github.com/kubernetes-sigs/container-object-storage-interface-provisioner-sidecar). | yes | `5` |
| sidecar.image.reposiotry | COSI driver sidecar container image repository. | yes | `"gcr.io/k8s-staging-sig-storage/objectstorage-sidecar/objectstorage-sidecar"` |
| sidecar.image.tag | COSI driver sidecar container image tag. | yes | `"v20230130-v0.1.0-24-gc0cf995"` |
| sidecar.image.pullPolicy | COSI driver sidecar container image pull policy. Maps 1-to-1 with [Kubernetes image pull policy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy). | yes | `"IfNotPresent"` |
| configuration.create | Specifies whether a secret with driver configuration should be created If set to false, you must set `configuration.secretName` field to an existing configuration secret name. | yes | `true` |
| configuration.secretName | Name can be used to specify an existing secret name to use for the driver configuration or override the generated name. | no | `"cosi-config"` |
| configuration.data | Data should be provided when installing chart, it will be used to create the Secret with the driver configuration. `configuration.create` must be set to `true` for this to work. | no | `""` |
{{</table>}}

> ℹ️ **NOTE:**
Expand Down