Redis

The Redis Helm chart provides a simple and efficient way to deploy Redis instances in your Kubernetes cluster. It is optimized for scalability, persistence, and performance, making it suitable for caching, messaging, and data storage workloads.

Prerequisites

• Kubernetes 1.19+
• Helm 3+

Add Helm Repository

Before deploying the Redis chart, add the repository to your Helm installation and update the repository index:

helm repo add zopdev https://helm.zop.dev
helm repo update

See Helm Repository Documentation for more information.

Install Helm Chart

To install the Redis Helm chart, execute the following command:

helm install [RELEASE_NAME] zopdev/redis

Replace [RELEASE_NAME] with the desired release name.

For example:

helm install my-redis zopdev/redis

To customize the deployment, use a custom values.yaml file or override values via command-line arguments.

See Helm Install Documentation for further details.

Uninstall Helm Chart

To uninstall the Redis Helm chart and remove all associated Kubernetes resources, use:

helm uninstall [RELEASE_NAME]

For example:

helm uninstall my-redis

See Helm Uninstall Documentation for additional details.

Configuration

The Redis Helm chart provides a variety of configurable parameters. The table below outlines the key configurations:

You can override these values in a values.yaml file or pass them as flags during installation.

Example values.yaml File

diskSize: "10Gi"

version: "6.2.13"

# Resource configuration
resources:
  requests:
    cpu: "500m"
    memory: "256M"
  limits:
    cpu: "1500m"
    memory: "1Gi"

To use this configuration, save it in a values.yaml file and apply it during installation:

helm install my-redis zopdev/redis -f values.yaml

Features

• Persistence: Store Redis data across pod restarts using persistent volume claims.
• Resource Optimization: Define resource requests and limits to suit your workload and cluster capacity.
• Rolling Updates: Ensure zero downtime during updates with the default RollingUpdate strategy.
• Customizable Configurations: Flexibly tailor the deployment using Helm values.

Advanced Usage

Custom Persistent Volume Configuration

You can customize the persistent volume size and storage class for Redis data by updating the values.yaml file:

diskSize: "50Gi"
storageClass: "fast-storage"

Scaling Redis

To scale Redis pods or create replicas, adjust the configuration to enable clustering. For example, use a stateful set for Redis replicas or Sentinel for high availability.

Pod Scheduling

nodeSelector, tolerations and affinity are passed straight through to the pod spec. All three are empty by default and render nothing, so leaving them unset changes nothing for an existing release.

Together they place the workload on a dedicated node pool — the nodeSelector picks the pool, the toleration gets past its taint:

nodeSelector:
  workload: stateful

tolerations:
  - key: workload
    operator: Equal
    value: stateful
    effect: NoSchedule

affinity takes a full Affinity object and is rendered verbatim.

Contributing

We welcome contributions to improve this Helm chart. Please refer to the CONTRIBUTING.md file for contribution guidelines.

Code of Conduct

To maintain a healthy and collaborative community, please adhere to our Code of Conduct.

License

This project is licensed under the LICENSE. Please review it for terms of use.

Connection Config

• REDIS_PORT : The port Redis is listening on.Default 6379.
• REDIS_HOST : The internal DNS hostname pointing to the Redis headless service.
• REDIS_URL : Full connection URL to Redis .