-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 Support on Kubernetes #10397
Comments
I'm not quite sure where this is going wrong, but it doesn't quite seem like an Immich issue to me. This seems like either an issue with the bitnami chart or kubernetes dns, or with how the redis library we use resolves the address. |
The Bitnami charts indeed lacks configuration by not providing ipFamily and/or ipFamilyPolicy, but an IPv6-only service should be working in the first place. Kubernetes DNS works fine, tested by installing ping in the pod then running:
This is expected because the service is IPv6-only, so AAAA records works fine but querying A returns no host. It does looks like an error in ioredis: https://github.com/redis/ioredis/blob/main/lib/redis/RedisOptions.ts#L201 |
You can set REDIS_URL (see https://immich.app/docs/install/environment-variables#redis), which expects base64-encoded json matching the RedisOptions type you linked. |
Thanks, that did work! |
It was done this way to support redis sentinel, which I believe isn't possible through that (admittedly more sensible) URL format. |
The bug
Immich cannot connect to Redis in Kubernetes in Dual-Stack mode because it only resolves IPv4 for Redis service, when the service is IPv6-only (and not configurable due to Bitnami's Redis chart).
It results in the following error in loop (because the service only has AAAA record and no A records):
The OS that Immich Server is running on
K8s v1.28.10
Version of Immich Server
1.106.4
Version of Immich Mobile App
N/A
Platform with the issue
Your docker-compose.yml content
N/A
Your .env content
Reproduction steps
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: