This message was deleted.
# generala
adamant-kite-43734
06/06/2023, 4:12 PMThis message was deleted.
c
creamy-pencil-82913
06/06/2023, 5:18 PMcheck for mutating webhooks
g
green-cat-8353
06/06/2023, 11:35 PMhmm, checked there - thanks for the idea though. Am I destined to grepping the output of a for loop grabbing all api-versions and looking for something that has the same formula as mutatingwebhooks?
green-cat-8353
06/06/2023, 11:35 PMEg UPDATE CREATE verbiage
c
creamy-pencil-82913
06/06/2023, 11:44 PMI’m assuming you’ve checked for a LimitRange in the namespace already? https://kubernetes.io/docs/concepts/policy/limit-range/
A LimitRange provides constraints that can:
• Set default request/limit for compute resources in a namespace and automatically inject them to Containers at runtime.
g
green-cat-8353
06/07/2023, 2:44 PMI haven't actually, let me try that too. That was it
green-cat-8353
06/07/2023, 2:44 PMyay! thanks!
green-cat-8353
06/12/2023, 4:24 PMSo I found the limitranges, deleted them but they re-appeared. I then looked at why, apparently re-created by norman, whoever/whatever that is, turned up a search result: https://forums.rancher.com/t/norman-keeps-adding-limitranges/37694
c
creamy-pencil-82913
06/12/2023, 4:40 PMyeah, so those would be defined in the rancher project that the namespaces are a part of
creamy-pencil-82913
06/12/2023, 4:41 PMcheck the project quota settings I think?
g
green-cat-8353
06/12/2023, 4:43 PMhmm, I was able to blank out the values in the edit project section
green-cat-8353
06/12/2023, 4:46 PMwhich in turn caused the values being applied at the pod to cpu 0 for both limits and requests
green-cat-8353
06/12/2023, 4:46 PMsigh
green-cat-8353
06/12/2023, 8:49 PMwhew, ok that was a head scratcher for a bit.
green-cat-8353
06/12/2023, 8:49 PMapparently the policy just needs blank fields for it to be unenforced, 0 is not empty here.
3 Views