Master RedisInsight: Install, Configure, and Use on Linux and Kubernetes
This guide walks you through installing RedisInsight, configuring its environment variables, deploying it on Kubernetes, and using its GUI to monitor Redis metrics, edit data, and analyze memory, complete with command‑line examples and visual screenshots.
1. RedisInsight Overview
RedisInsight is an intuitive and efficient GUI management tool for Redis. It monitors memory usage, connection count, hit rate, and uptime, and allows interaction with Redis via the built‑in CLI while supporting Redis modules.
Official documentation: https://docs.redis.com/latest/ri/
Key features:
Only GUI tool that supports Redis Cluster.
Browser‑based interface for searching keys, viewing, and editing data.
Supports SSL/TLS connections and provides in‑app memory analysis.
2. RedisInsight Installation and Usage
1. Physical Installation
1. Download the RedisInsight package: https://redis.com/redis-enterprise/redis-insight
[root@Redis ~]# ls
anaconda-ks.cfg redisinsight-linux64-1.11.0
[root@Redis ~]# mkdir /usr/local/redisinsight
[root@Redis ~]# mv redisinsight-linux64-1.11.0 /usr/local/redisinsight/redisinsight-1.11.0
[root@Redis ~]# chmod +x /usr/local/redisinsight/redisinsight-1.11.02. Configure environment variables for RedisInsight:
[root@Redis ~]# echo "export REDISINSIGHT_HOST=192.168.1.1" >> ~/.bash_profile
[root@Redis ~]# echo "export REDISINSIGHT_HOST_DIR=/usr/local/redisinsight/.redisinsight" >> ~/.bash_profile
[root@Redis ~]# source ~/.bash_profileAnnotations:
REDISINSIGHT_PORT – listening port (default: 8001).
REDISINSIGHT_HOST – IP address (default: 0.0.0.0).
LOG_DIR – log storage path (default: REDISINSIGHT_HOST_DIR).
REDISINSIGHT_HOST_DIR – data storage path (default: ~/.redisinsight).
3. Start the RedisInsight service:
[root@Redis ~]# nohup /usr/local/redisinsight/redisinsight-linux64-1.4.0 & // run in background
[root@Redis ~]# ps aux | grep redis // verify the process2. Kubernetes Installation
1. Create a redisinsight.yaml file:
apiVersion: v1
kind: Service
metadata:
name: redisinsight-service
spec:
type: NodePort
ports:
- port: 80
targetPort: 8001
nodePort: 31888
selector:
app: redisinsight
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: redisinsight
labels:
app: redisinsight
spec:
replicas: 1
selector:
matchLabels:
app: redisinsight
template:
metadata:
labels:
app: redisinsight
spec:
containers:
- name: redisinsight
image: redislabs/redisinsight:1.7.0
imagePullPolicy: IfNotPresent
volumeMounts:
- name: db
mountPath: /db
ports:
- containerPort: 8001
protocol: TCP
volumes:
- name: db
emptyDir: {}2. Deploy the manifest:
[root@Redis ~]# kubectl apply -f redisinsight.yaml3. Basic Usage
If Redis is not yet installed, install it first:
[root@Redis ~]# wget https://download.redis.io/releases/redis-6.2.6.tar.gz
[root@Redis ~]# tar zxf redis-6.2.6.tar.gz
[root@Redis ~]# cd redis-6.2.6
[root@Redis ~]# make PREFIX=/usr/local/redis install
[root@Redis ~]# sed -i '/^bind 127.0.0.1/s/127.0.0.1/192.168.1.1/g' redis.conf # change bind IP
[root@Redis ~]# sed -i '/protected-mode/s/yes/no/g' redis.conf # disable protected mode
[root@Redis ~]# sed -i '/daemonize/s/no/yes/g' redis.conf # enable daemon
[root@Redis ~]# sed -i '/requirepass/s/foobared/123123/g' redis.conf # set password
[root@Redis ~]# sed -i '/requirepass 123123/s/^#//g' redis.conf # uncomment password line
[root@Redis ~]# cp redis.conf /usr/local/redis/
[root@Redis ~]# /usr/local/redis/bin/redis-server /usr/local/redis/redis.confAccess the RedisInsight UI using the configured IP and port (e.g., http://192.168.1.1:8001). The interface lets you:
View various Redis metrics and information.
Perform CRUD operations directly from the UI.
Analyze memory usage visually.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Architect's Tech Stack
Java backend, microservices, distributed systems, containerized programming, and more.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
