This message was deleted.
# k3s
a
This message was deleted.
1
q
One common approach is to use a shared redis or memcached (or any other similar type of service). You probably want to aim for network+memory instead of network+disk for that kind of thing (depending on your needs ofc).
k
I would prefer a memory approach, ya.. It's a non-issue if the caching suddenly gets whiped, but they need to be equal over all running pods.
q
In that case, I would look at deploying a redis instance in the cluster and use that. You could optionally go for a HA setup using Sentinel, but that's often more complexity than it's worth for a simple cache.
1
k
Aight, I wasn't yet aware of https://redis.io/, so thanks for the feedback 😄