Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
a
agreeable-mouse-95550
07/08/2022, 1:33 AMHi folks. I’m comparing a few different Kubernetes variants, looking into how much memory they use per CRD installed. Note that I mean literally per CustomResourceDefinition that is created - not per custom resource. I’m seeing
k3s serverc
creamy-pencil-82913
07/08/2022, 1:48 AMI don't think that's something we've ever tuned for or benchmarked against, but yeah I would expect it to be the same as upstream.
a
agreeable-mouse-95550
07/08/2022, 2:00 AMHaha I figured. I don’t think it’s something most folks think about until it becomes a problem. 🙂 Thanks!
We’re into the low thousands of CRDs in Crossplane so we’re seeing API server memory usage climbing above 5GBs.
Interestingly https://github.com/kcp-dev/kcp seems to be the best in this regard - they’re at something like 1-2MiB/CRD. I thought that might be because they’re lacking a bunch of OpenAPI functionality, but if I understand correctly k3s dropped some of that too.