{client="service-ca-operator/v0.0.0 (linux/amd64) kubernetes/$Format",resource="configmaps",scope="namespace",verb="GET"} 1.6111111111111112 {client="service-ca-operator/v0.0.0 (linux/amd64) kubernetes/$Format",resource="configmaps",scope="namespace",verb="PUT"} 1.5370370370370372 This is reads and writes per second, it looks like a hot loop. Must fix for GA because it impacts total write load on cluster.
Looks like the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=1703232 Working to fix it.
https://github.com/kubernetes/kubernetes/pull/77204 https://github.com/kubernetes-sigs/controller-runtime/pull/412
Currently controller-runtime repo runs leader election with hard-coded, very agressive values. With above PRs, leader election configuration will become configurable. Then we would pass higher time durations from cluster-autoscaler-operator using the options which above PRs are adding.
(In reply to Vikas Choudhary from comment #4) > Currently controller-runtime repo runs leader election with hard-coded, very > agressive values. With above PRs, leader election configuration will become > configurable. Then we would pass higher time durations from > cluster-autoscaler-operator using the options which above PRs are adding. Service CA does not use controller-runtime
Verified on 4.1.0-0.nightly-2019-05-04-210601. {client="service-ca-operator/v0.0.0 (linux/amd64) kubernetes/$Format",code="200",contentType="application/json",endpoint="https",instance="10.0.148.133:6443",job="apiserver",namespace="default",resource="configmaps",scope="namespace",service="kubernetes",verb="GET"} 0.1 {client="service-ca-operator/v0.0.0 (linux/amd64) kubernetes/$Format",code="200",contentType="application/json",endpoint="https",instance="10.0.148.133:6443",job="apiserver",namespace="default",resource="configmaps",scope="namespace",service="kubernetes",verb="PUT"} 0.1 {client="service-ca-operator/v0.0.0 (linux/amd64) kubernetes/$Format",code="200",contentType="application/json",endpoint="https",instance="10.0.172.173:6443",job="apiserver",namespace="default",resource="configmaps",scope="namespace",service="kubernetes",verb="GET"} 0.3 {client="service-ca-operator/v0.0.0 (linux/amd64) kubernetes/$Format",code="200",contentType="application/json",endpoint="https",instance="10.0.172.173:6443",job="apiserver",namespace="default",resource="configmaps",scope="namespace",service="kubernetes",verb="PUT"} 0.3
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-2019:0758