https://github.com/CommercialTribe/kube-redis

Redis on Kubernetes as StatefulSet
https://github.com/CommercialTribe/kube-redis

kubernetes redis statefulsets

Last synced: about 1 month ago
JSON representation

Redis on Kubernetes as StatefulSet

• Host: GitHub
• URL: https://github.com/CommercialTribe/kube-redis
• Owner: CommercialTribe
• License: mit
• Archived: true
• Created: 2017-02-17T16:57:24.000Z (over 7 years ago)
• Default Branch: develop
• Last Pushed: 2017-09-06T20:44:39.000Z (about 7 years ago)
• Last Synced: 2024-06-01T11:35:39.986Z (3 months ago)
• Topics: kubernetes, redis, statefulsets
• Language: Shell
• Homepage:
• Size: 77.1 KB
• Stars: 34
• Watchers: 7
• Forks: 22
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-kubernetes - Redis on Kubernetes as StatefulSet - The following document describes the deployment of a self-bootstrapping, reliable, multi-node Redis on Kubernetes. (Performance)

README

        
# Redis on Kubernetes as StatefulSet

The following document describes the deployment of a self-bootstrapping, reliable,

multi-node Redis on Kubernetes. It deploys a master with replicated slaves, as

well as replicated redis sentinels which are use for health checking and failover.

## Prerequisites

This example assumes that you have a Kubernetes cluster installed and running,

and that you have installed the kubectl command line tool somewhere in your path.

Please see the getting started for installation instructions for your platform.

### Storage Class

This makes use of a StorageClass, either create a storage class with the name of

"ssd" or update the StatefulSet to point to to the correct StorageClass.

## Running

To get your cluster up and running simple run:

`kubectl apply -Rf k8s`

The cluster will automatically bootstrap itself.

### Caveats

Your pods may not show up in the dashboard. This is because we automatically add

additional labels to the pods to recognize the master. To see the pods within the

dashboard you should look at the redis-nodes service instead.