Open 2rs2ts opened 5 years ago
It depends on your workloads and traffic i think, I would profile it and set it to a sensible amount in your environment. In production we request cpu and memory, and limit the memory to a 128mb to deal with potential memory leaks. We don't limit the CPU as throttling could/can cause issues, and you want to guarantee service. We deem the server and agent to be priorityClassName: system-node-critical
as a lot of our services rely on IAM, and we don't want it to be evicted. This is brief but hope this helps.
There don't seem to be any benchmarks published here for kiam, nor any recommendations for how much resources to allocate for it. A recommended configuration in the sample deploys would be very useful so users don't need to set up their own benchmarking tests. Surely, a lot of benchmarking work has been duplicated because it's been done redundantly by isolated users.