This message was deleted.
# k3s
a
This message was deleted.
c
Resources requests/limits are not really a security measure. And given how difficult it is to modify those manifests since they are not helm charts, we're reluctant to set any defaults that would restrict people from scaling up.
1
a
@creamy-pencil-82913 is the above true for system-upgrade-controller pod aswell?
• coredns-64fd4b4794-wm58k (missing CPU limit) • local-path-provisioner-774c6665dc-bmb44 (missing CPU requests/limits) • metrics-server-7bfffcd44-8hszq (missing CPU limit) • system-upgrade-controller pods (missing all resource specifications) some have missing limits only. suc neither has limits nor requests
c
Is there a problem? All of these should consume minimal resources, and leaving them unspecified shouldn't harm anything.
a
no functional problems with it. Some of our customers want resource block defined as part of their policy. Pods will get guaranteed resources. wdyt?