This message was deleted.
# k3sa
adamant-kite-43734
09/29/2022, 6:16 PMThis message was deleted.
c
creamy-pencil-82913
09/29/2022, 9:34 PMI think you might be exceeding the design goals of both etcd and kubernetes. If you’ve got so much data that etd itself is refusing to store it, simply switching the storage backend to kine+sql probably isn’t going to be a material improvement.
creamy-pencil-82913
09/29/2022, 9:35 PMSounds like perhaps some other rbac-enabled kv store or document store might be a better fit for your use case?
c
creamy-waiter-66684
09/30/2022, 5:30 PMHmmm
creamy-waiter-66684
09/30/2022, 5:31 PMWe wanted to take advantage of some of the benefits of the API server (provided API, version conversion of CRs, etc).
creamy-waiter-66684
09/30/2022, 5:31 PMIs this amount of memory usage by k3s expected though?
creamy-waiter-66684
09/30/2022, 5:31 PMDoes k3s cache these objects as they are inserted?
c
creamy-pencil-82913
09/30/2022, 6:01 PMnot K3s specifically no, but Kubernetes does do a lot of caching yes.
creamy-pencil-82913
09/30/2022, 6:02 PMYou might try putting some memory limits on the k3s systemd unit to encourage it to be a little more conservative but at the end of the day you’re just kinda using it in a way it wasn’t really designed for.
creamy-pencil-82913
09/30/2022, 6:02 PMIt’s not meant to be a document/blob store. It’s an orchestration platform.
creamy-pencil-82913
09/30/2022, 6:05 PMYou might look at https://github.com/kcp-dev/kcp if all you want is CRDs without the orchestration bit?
creamy-pencil-82913
09/30/2022, 6:05 PMit’s experimental though
4 Views