Kiran Mova
eb706609d9
* Upgrade to openebs 0.6 Includes changes to: - Change the image tags to 0.6 - Add a new deployment introduced in 0.6 for supporting snapshots - Identation fix with templates - Updated README and Chart.yaml Signed-off-by: kmova <kiran.mova@openebs.io> * Fix lint errors with spaces Signed-off-by: kmova <kiran.mova@openebs.io> * Maintain consistency with punctuation in clusterrole.yaml Signed-off-by: kmova <kiran.mova@mayadata.io> * Fix the toleration and affinity specs Signed-off-by: kmova <kiran.mova@mayadata.io>
OpenEBS
OpenEBS is an open source storage platform that provides persistent and containerized block storage for DevOps and container environments.
OpenEBS can be deployed on any Kubernetes cluster - either in cloud, on-premise or developer laptop (minikube). OpenEBS itself is deployed as just another container on your cluster, and enables storage services that can be designated on a per pod, application, cluster or container level.
Introduction
This chart bootstraps OpenEBS deployment on a Kubernetes cluster using the Helm package manager.
Prerequisites
- Kubernetes 1.7.5+ with RBAC enabled
- iSCSI PV support in the underlying infrastructure
Installing OpenEBS
helm install stable/openebs
Installing OpenEBS with the release name my-release:
helm install --name `my-release` stable/openebs
To uninstall/delete the my-release deployment:
helm ls --all
helm delete `my-release`
Configuration
The following table lists the configurable parameters of the OpenEBS chart and their default values.
| Parameter | Description | Default |
|---|---|---|
rbac.create |
Enable RBAC Resources | true |
serviceAccount.create |
Specify if Service Account should be created | true |
serviceAccount.name |
Specify the name of service account | openebs-maya-operator |
image.pullPolicy |
Container pull policy | IfNotPresent |
apiserver.image |
Docker Image for API Server | openebs/m-apiserver |
apiserver.imageTag |
Docker Image Tag for API Server | 0.6.0 |
apiserver.replicas |
Number of API Server Replicas | 1 |
provisioner.image |
Docker Image for Provisioner | openebs/openebs-k8s-provisioner |
provisioner.imageTag |
Docker Image Tag for Provisioner | 0.6.0 |
provisioner.replicas |
Number of Provisioner Replicas | 1 |
snapshotOperator.provisioner.image |
Docker Image for Snapshot Provisioner | openebs/snapshot-provisioner |
snapshotOperator.provisioner.imageTag |
Docker Image Tag for Snapshot Provisioner | 0.6.0 |
snapshotOperator.controller.image |
Docker Image for Snapshot Controller | openebs/snapshot-controller |
snapshotOperator.controller.imageTag |
Docker Image Tag for Snapshot Controller | 0.6.0 |
snapshotOperator.replicas |
Number of Snapshot Operator Replicas | 1 |
jiva.image |
Docker Image for Jiva | openebs/jiva |
jiva.imageTag |
Docker Image Tag for Jiva | 0.6.0 |
jiva.replicas |
Number of Jiva Replicas | 3 |
jiva.replicaNodeSelector.enabled |
Enable scheduling replicas with node selector | false |
jiva.replicaNodeSelector.value |
node labels assigned to replica pods | nodetype=storage |
Specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
helm install --name `my-release` -f values.yaml stable/openebs
Tip
: You can use the default values.yaml