-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Give guidance that memcached should not be configured on loadbalancer level #3879
Comments
AFAIK you can use DNS service discovery or you can specify all. i.e thanos/pkg/cacheutil/memcached_client.go Line 81 in befb025
Kubernetes e.g https://github.com/observatorium/deployments/blob/258c17c7889351cc7366a5c3b6162ad216d666d0/components/thanos.libsonnet#L241 @pstibrany @pracucci would know better. But yes, let's improve documentation on this. |
Right, thanks @kakkoyun . I will include that as well. It's important to either use such DNS discovery or define the single targets yourself (in case of for example AWS). If you only define the k8s svc, you are going to have a bad time :) |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
The
Can be used in various ways. It should be clear that each memcached instance should be defined, rather than a 'main' instance E.g. "loadbalancer" adres. This is because the client does not do autodiscovery (Correct me if I'm wrong): https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/AutoDiscovery.HowAutoDiscoveryWorks.html
Plan
I will update the documentation to make this clear
The text was updated successfully, but these errors were encountered: