Change Details

See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ The important thing to know is that requests can be set in k8s and they tell k8s that a given host must have X ram/cpu available in order to schedule the pods on that host. They do *not* perform throttling of CPU or cause OOMKills; those roles are handled by k8s limits which are out of scope of this ticket. AC [] Requests set for any cirrus-streaming-updater pods

See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ The important thing to know is that requests can be set in k8s and they tell k8s that a given host must have X ram/cpu available in order to schedule the pods on that host. They do *not* perform throttling of CPU or cause OOMKills; those roles are handled by k8s limits which are out of scope of this ticket. AC [] Requests set for any cirrus-streaming-updater containers

See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ The important thing to know is that requests can be set in k8s and they tell k8s that a given host must have X ram/cpu available in order to schedule the pods on that host. They do *not* perform throttling of CPU or cause OOMKills; those roles are handled by k8s limits which are out of scope of this ticket. AC [] Requests set for any cirrus-streaming-updater podscontainers