[Bug]: RedisInsight saves IP instead of DNS name for cluster and fails to reconnect if internal IP changes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 491
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
I have a redis cluster on kubernetes, and I connect to it though a nodeport. RedisInsight saves the IP instead of the DNS name for the cluster, and when the IP changes, it's unable to reconnect. As I cannot change the host in the connection, I'm frequently deleting the host and recreating it in order to connect to redis.
Steps to reproduce (How to reproduce what you found step by step)
Add the cluster as "redis.internaldomain.com, port 30123", redis.internaldomain.com points to 10.100.33.155
Actual behavior (A short description of what you found)
The connection is added, but shows as "172.31.14.83:6379" in the listing. This doesn't happen with the standalong redis, only cluster.
Expected behavior (A short description of what you expected to find)
The connection should show as "redis.internaldomain.com:30123", and redis should do a dns lookup everytime it tries to connect in order to discover the topology.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the cluster connection with redis.internaldomain.com on port 30123 and observe the saved connection listing. Trace the cluster connection and topology-discovery entry points to determine where the DNS name is replaced by an internal IP. Done means the listing retains the DNS name and reconnect attempts resolve the DNS name while discovering the cluster topology.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, redis
- Domain
- databases, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100