@helm-charts/appscode-kubedb
KubeDB by AppsCode - Production ready databases on Kubernetes
Field | Value |
---|
Repository Name | appscode |
Chart Name | kubedb |
Chart Version | 0.9.0-rc.2 |
NPM Package Version | 0.1.0 |
Helm chart `values.yaml` (default values)
replicaCount: 1
kubedb:
registry: kubedb
repository: operator
tag: 0.9.0-rc.2
cleaner:
registry: appscode
repository: kubectl
tag: v1.11
imagePullPolicy: IfNotPresent
criticalAddon: false
logLevel: 3
annotations: {}
nodeSelector:
beta.kubernetes.io/os: linux
beta.kubernetes.io/arch: amd64
tolerations: {}
affinity: {}
rbac:
create: true
serviceAccount:
create: true
name:
apiserver:
groupPriorityMinimum: 10000
versionPriority: 15
enableMutatingWebhook: true
enableValidatingWebhook: true
ca: not-ca-cert
disableStatusSubresource: false
bypassValidatingWebhookXray: false
useKubeapiserverFqdnForAks: true
enableAnalytics: true
KubeDB
KubeDB by AppsCode - Making running production-grade databases easy on Kubernetes
TL;DR;
$ helm repo add appscode https://charts.appscode.com/stable/
$ helm repo update
$ helm install appscode/kubedb
Introduction
This chart bootstraps a KubeDB controller deployment on a Kubernetes cluster using the Helm package manager.
Prerequisites
Installing the Chart
To install the chart with the release name my-release
:
$ helm install appscode/kubedb --name my-release
The command deploys KubeDB operator on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Tip: List all releases using helm list
Uninstalling the Chart
To uninstall/delete the my-release
:
$ helm delete my-release
The command removes all the Kubernetes components associated with the chart and deletes the release.
Configuration
The following table lists the configurable parameters of the KubeDB chart and their default values.
Parameter | Description | Default |
---|
replicaCount | Number of kubedb operator replicas to create (only 1 is supported) | 1 |
kubedb.registry | Docker registry used to pull Kubedb operator image | kubedb |
kubedb.repository | Kubedb operator container image | operator |
kubedb.tag | Kubedb operator container image tag | 0.9.0-rc.2 |
cleaner.registry | Docker registry used to pull Webhook cleaner image | appscode |
cleaner.repository | Webhook cleaner container image | kubectl |
cleaner.tag | Webhook cleaner container image tag | v1.11 |
imagePullSecrets | Specify image pull secrets | nil (does not add image pull secrets to deployed pods) |
imagePullPolicy | Image pull policy | IfNotPresent |
criticalAddon | If true, installs KubeDB operator as critical addon | false |
logLevel | Log level for operator | 3 |
affinity | Affinity rules for pod assignment | {} |
annotations | Annotations applied to operator pod(s) | {} |
nodeSelector | Node labels for pod assignment | {} |
tolerations | Tolerations used pod assignment | {} |
rbac.create | If true , create and use RBAC resources | true |
serviceAccount.create | If true , create a new service account | true |
serviceAccount.name | Service account to be used. If not set and serviceAccount.create is true , a name is generated using the fullname template | `` |
apiserver.groupPriorityMinimum | The minimum priority the group should have. | 10000 |
apiserver.versionPriority | The ordering of this API inside of the group. | 15 |
apiserver.enableValidatingWebhook | Enable validating webhooks for KubeDB CRDs | true |
apiserver.enableMutatingWebhook | Enable mutating webhooks for KubeDB CRDs | true |
apiserver.ca | CA certificate used by main Kubernetes api server | not-ca-cert |
apiserver.disableStatusSubresource | If true, disables status sub resource for crds. Otherwise enables based on Kubernetes version | false |
apiserver.bypassValidatingWebhookXray | If true, bypasses validating webhook xray checks | false |
apiserver.useKubeapiserverFqdnForAks | If true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522 | true |
enableAnalytics | Send usage events to Google Analytics | true |
Specify each parameter using the --set key=value[,key=value]
argument to helm install
. For example:
$ helm install --name my-release --set image.tag=v0.2.1 appscode/kubedb
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 --values values.yaml appscode/kubedb
RBAC
By default the chart will not install the recommended RBAC roles and rolebindings.
You need to have the flag --authorization-mode=RBAC
on the api server. See the following document for how to enable RBAC.
To determine if your cluster supports RBAC, run the following command:
$ kubectl api-versions | grep rbac
If the output contains "beta", you may install the chart with RBAC enabled (see below).
Enable RBAC role/rolebinding creation
To enable the creation of RBAC resources (On clusters with RBAC). Do the following:
$ helm install --name my-release appscode/kubedb --set rbac.create=true