immich-app
Update kubernetes.md
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated |
|---|---|---|---|---|
| immich-code-coverage | ✅ Ready (Inspect) | Visit Preview | 💬 Add your feedback | Jan 25, 2023 at 8:35PM (UTC) |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
@gregwalters is attempting to deploy a commit to the immich Team on Vercel.
A member of the Team first needs to authorize it.
I'm not sure how I feel about the ndots solution. It does technically fix the geocoder, but it's likely to break other in-cluster dns lookups for eg. a database I another namespace.
I'm not sure how I feel about the ndots solution. It does technically fix the geocoder, but it's likely to break other in-cluster dns lookups for eg. a database I another namespace.
Sure, but none of the solutions outlined in the documentation are ideal. Might as well have another option available in the pile of less than stellar options.
What's wrong with the searchdomain fix? That's the general-purpose solution that also removes the issue for any other alpine containers.
In my case, the search domain is set via DHCP and removing it from my nodes would remove it from everything on my network and that's a no-go. I enjoy not having to type fully-qualified hostnames in various configs and such. Even if I were to set my nodes to ignore the search domain, I'd still rather not.
Asking "what's wrong with removing the search domain" is ignoring every valid use case for having a search domain and the existence of that option in general.
Unfortunate that this was closed. It seems to ignore my reasoning, doesn't describe why my suggestion isn't acceptable, and leaves a bad taste in my mouth that'll influence my decision to make future contributions or not.