Description of problem: A large cluster with either of the following: 1. a large amount of HPAs 2. a large amount of pods that are always unhealthy is causing too many writes to the API server and inducing excessive snapshot of etcd. Version-Release number of selected component (if applicable): OCP 3.6.0 How reproducible: Always Steps to Reproduce: See above Actual results: spam should be reduced to masters Expected results: HPA should only send status updates if status changes Pods in perpetual failure status should not spam masters with events Additional info:
Two fixes were identified: https://github.com/openshift/origin/pull/14747 this sets a budget of events about an object. per source+object event budget of 25 burst with refill of 1 every 5 minutes. it will reduce the long tail of events sent about objects in perpetual failure states (pod in crash loop backoff, controllers denied by quota, etc.). https://github.com/openshift/origin/pull/14529 HPA only sends status updates if status changes.
I'm using this bz to track only https://github.com/openshift/origin/pull/14747 The HPA fix is tracked in 1467022
Hi Mike, help verify the bug, thanks.
Verified during an event storm caused by misconfigured DNS. api servers were not getting unique PUTs for each event recorded by the kubelet. v3.6.126.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188