Description of problem: because quorum-guard is using hostNetwork all network traffic to be counted as a container traffic, so some pods had > 4MBps network in/out in console. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: quorum-guard preforms localhost checks against host 127.0.0.1 and is counted as container traffic. Expected results:quorum-guard preforms localhost checks against host 127.0.0.1 without be counted as container traffic. Additional info:
Verification steps. stand up prometheus based on prom data file from the following PR run. https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1552/pull-ci-openshift-machine-config-operator-master-e2e-aws/6758 query container_network_transmit_bytes_total{name="k8s_POD_etcd-quorum-guard-f9fc8d4c-6x4g5_openshift-machine-config-operator_a7a8ac88-81ac-4b37-bdc9-e148c88a53e7_0"} result is max of about 483.9 k of traffic. see attached file (4.5-fixed.png) Before this patfch you can see container traffic in the hundreds of mb see (4.5-before-fix.png)
Created attachment 1680326 [details] 4.5-fixed.png
Created attachment 1680327 [details] 4.5-before-fix.png
Verified with steps of Sam updated, thanks!
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/RHBA-2020:2409