This message was deleted.
# k3da
adamant-kite-43734
05/26/2023, 12:04 PMThis message was deleted.
w
wide-garage-9465
05/26/2023, 12:13 PMk3d does not hide any functionality.
You can use everything that K3s exposes.
See K3s options: https://docs.k3s.io/cli/server
wide-garage-9465
05/26/2023, 12:14 PMIn k3d, you pass the flags to K3s via
Copy code
--k3s-arg ARG@NODEFILTER[;@NODEFILTER] Additional args passed to k3s command (Format: ARG@NODEFILTER[;@NODEFILTER])f
flat-bird-89111
05/26/2023, 12:16 PMThanks for the quick response! However I see no option to configure the storage limit. Can you point me to the flag?
flat-bird-89111
05/26/2023, 12:17 PMIs that via ``--etcd-arg``?
w
wide-garage-9465
05/26/2023, 12:32 PMTHe K3s docs show you all available flags to configure etcd in K3s.
@creamy-pencil-82913 is there anything else exposed or possible, e.g. via env vars?
c
creamy-pencil-82913
05/26/2023, 2:33 PMYeah, --etcd-arg would be the way to go.
f
flat-bird-89111
05/26/2023, 2:36 PMYes, I configured it via
--k3s-arg "--etcd-arg=quota-backend-bytes=8589934592@server:*" Copy code
/ # cat /var/lib/rancher/k3s/server/db/etcd/config | tail -2
quota-backend-bytes: 8589934592flat-bird-89111
05/26/2023, 2:41 PMOne thing I don’t understand is the free db size when I get it from etcdctl, per this post, the free space is dbSize-dbSizeInUse:
Let’s use the first endpoint as an example, itsMy result doesn’t seem to be align with that though, my “dbSize”:291110912 and “dbSizeInUse”:160505856.is 5177344 bytes, anddbSizeis 2039808 bytes. It means that there are (5177344-2039808) bytes of free space, which can be reclaimed by executing the defragmentation operation.dbSizeInUse
c
creamy-pencil-82913
05/26/2023, 3:35 PMIf you have specific questions about etcd, you might take them to the etcd project maintainers?
f
flat-bird-89111
05/26/2023, 3:36 PMright, I figured this may not be the right channel for such questions. Thanks for you explaination!
65 Views