[BUG?] Redis image support IPv6
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Describe the bug
We are setting an IPv4 address for Redis liveness and readiness probes:
https://github.com/pulp/pulp-operator/blob/05bc5969c84b9040658acfcc4159a79602116488/controllers/repo_manager/redis.go#L286
https://github.com/pulp/pulp-operator/blob/05bc5969c84b9040658acfcc4159a79602116488/controllers/repo_manager/redis.go#L307
We should validate if this could have issues in environments with only IPv6 enabled.
We would also need to check if the image supports IPv6.
To Reproduce
I didn't reproduce this error, this issue needs more investigation.
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
Inspect controllers/repo_manager/redis.go at the liveness and readiness probe references around lines 286 and 307. Verify whether the configured IPv4 address and the Redis image work in an IPv6-only environment. Done means the IPv6 compatibility question is answered and any necessary probe or image change is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, redis
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100