You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.
New to KubeDB? Please start here.
Redis is a Kubernetes
Custom Resource Definitions (CRD). It provides declarative configuration for Redis in a Kubernetes native way. You only need to describe the desired database configuration in a Redis object, and the KubeDB operator will create Kubernetes objects in the desired state for you.
As with all other Kubernetes objects, a Redis needs
metadata fields. It also needs a
.spec section. Below is an example Redis object.
apiVersion: kubedb.com/v1alpha2 kind: Redis metadata: name: r1 namespace: demo spec: version: 6.0.6 mode: Cluster cluster: master: 3 replicas: 1 storage: storageClassName: "standard" accessModes: - ReadWriteOnce resources: requests: storage: 1Gi monitor: agent: prometheus.io/operator prometheus: serviceMonitor: labels: app: kubedb interval: 10s configSecret: name: rd-custom-config podTemplate: metadata: annotations: passMe: ToDatabasePod controller: annotations: passMe: ToStatefulSet spec: serviceAccountName: my-service-account schedulerName: my-scheduler nodeSelector: disktype: ssd imagePullSecrets: - name: myregistrykey args: - "--loglevel verbose" env: - name: ENV_VARIABLE value: "value" resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" serviceTemplates: - alias: primary metadata: annotations: passMe: ToService spec: type: NodePort ports: - name: http port: 9200 terminationPolicy: Halt
spec.version is a required field specifying the name of the RedisVersion crd where the docker images are specified. Currently, when you install KubeDB, it creates the following
spec.mode specifies the mode in which Redis server instance(s) will be deployed. The possible values are either
"Cluster". The default value is
Standalone: In this mode, the operator to starts a standalone Redis server.
Cluster: In this mode, the operator will deploy Redis cluster.
spec.mode is set to
"Cluster", users can optionally provide a cluster specification. Currently, the following two parameters can be configured:
spec.cluster.master: specifies the number of Redis master nodes. It must be greater or equal to 3. If not set, the operator set it to 3.
spec.cluster.replicas: specifies the number of replica nodes per master. It must be greater than 0. If not set, the operator set it to 1.
PodDisruptionBudget to ensure that majority of these cluster replicas are available during voluntary disruptions so that quorum is maintained and no data loss is occurred.
spec.modeis set to
spec.replicasfield is ignored.
Since 0.10.0-rc.0, If you set
spec.storage is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. You can specify any StorageClass available in your cluster with appropriate resource requests.
spec.storage.storageClassNameis the name of the StorageClass used to provision PVCs. PVCs don’t necessarily have to request a class. A PVC with its storageClassName set equal to "" is always interpreted to be requesting a PV with no class, so it can only be bound to PVs with no class (no annotation or one set equal to “”). A PVC with no storageClassName is not quite the same and is treated differently by the cluster depending on whether the DefaultStorageClass admission plugin is turned on.
spec.storage.accessModesuses the same conventions as Kubernetes PVCs when requesting storage with specific access modes.
spec.storage.resourcescan be used to request specific quantities of storage. This follows the same resource model used by PVCs.
To learn how to configure
spec.storage, please visit the links below:
Redis managed by KubeDB can be monitored with builtin-Prometheus and Prometheus operator out-of-the-box. To learn more,
spec.configSecret is an optional field that allows users to provide custom configuration for Redis. This field accepts a
VolumeSource. So you can use any kubernetes supported volume source such as
azureDisk etc. To learn more about how to use a custom configuration file see here.
KubeDB allows providing a template for database pod through
spec.podTemplate. KubeDB operator will pass the information provided in
spec.podTemplate to the StatefulSet created for Redis server.
KubeDB accept following fields to set in
Uses of some field of
spec.podTemplate is described below,
spec.podTemplate.spec.args is an optional field. This can be used to provide additional arguments to database installation.
spec.podTemplate.spec.env is an optional field that specifies the environment variables to pass to the Redis docker image.
Note that, KubeDB does not allow to update the environment variables. If you try to update environment variables, KubeDB operator will reject the request with following error,
Error from server (BadRequest): error when applying patch: ... for: "./redis.yaml": admission webhook "redis.validators.kubedb.com" denied the request: precondition failed for: ... At least one of the following was changed: apiVersion kind name namespace spec.storage spec.podTemplate.spec.nodeSelector spec.podTemplate.spec.env
KubeDB provides the flexibility of deploying Redis server from a private Docker registry. To learn how to deploy Redis from a private registry, please visit here.
spec.podTemplate.spec.nodeSelector is an optional field that specifies a map of key-value pairs. For the pod to be eligible to run on a node, the node must have each of the indicated key-value pairs as labels (it can have additional labels as well). To learn more, see here .
serviceAccountName is an optional field supported by KubeDB Operator (version 0.13.0 and higher) that can be used to specify a custom service account to fine tune role based access control.
If this field is left empty, the KubeDB operator will create a service account name matching Redis crd name. Role and RoleBinding that provide necessary access permissions will also be generated automatically for this service account.
If a service account name is given, but there’s no existing service account by that name, the KubeDB operator will create one, and Role and RoleBinding that provide necessary access permissions will also be generated for this service account.
If a service account name is given, and there’s an existing service account by that name, the KubeDB operator will use that existing service account. Since this service account is not managed by KubeDB, users are responsible for providing necessary access permissions manually. Follow the guide here to grant necessary permissions in this scenario.
spec.podTemplate.spec.resources is an optional field. This can be used to request compute resources required by the database pods. To learn more, visit here.
You can also provide a template for the services created by KubeDB operator for Redis server through
spec.serviceTemplate. This will allow you to set the type and other properties of the services.
KubeDB allows following fields to set in
See here to understand these fields in detail.
terminationPolicy gives flexibility whether to
nullify(reject) the delete operation of
Redis crd or which resources KubeDB should keep or delete when you delete
Redis crd. KubeDB provides following four termination policies:
DoNotTerminate, KubeDB takes advantage of
ValidationWebhook feature in Kubernetes 1.9.0 or later clusters to implement
DoNotTerminate feature. If admission webhook is enabled,
DoNotTerminate prevents users from deleting the database as long as the
spec.terminationPolicy is set to
Following table show what KubeDB does when you delete Redis crd for different termination policies,
|1. Block Delete operation||✓||✗||✗||✗|
|2. Create Dormant Database||✗||✓||✗||✗|
|3. Delete StatefulSet||✗||✓||✓||✓|
|4. Delete Services||✗||✓||✓||✓|
|5. Delete PVCs||✗||✗||✓||✓|
|6. Delete Secrets||✗||✗||✗||✓|
If you don’t specify
spec.terminationPolicy KubeDB uses
Halt termination policy by default.