You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
While trying to understand the HVPA behaviour, I noticed bogus scale up/down cpu/memory messages that seem unrelated to what is actually hapenning.
Expected behaviour:
Log messages matching prev/next settings for cpu/memory.
How To Reproduce (as minimally and precisely as possible):
n/a
Logs:
From our aws-us1 seed:
2022-04-09T05:57:31.272255897Z: minutes after last scaling\\\"=122.67120271645 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=0\"
2022-04-09T05:57:31.272346973Z: vpa recommends changes?\\\"=false\"
2022-04-09T05:57:54.985066890Z: minutes after last scaling\\\"=123.06641621076666 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=1\"
2022-04-09T05:57:54.985153913Z: vpa recommends changes?\\\"=false\"
2022-04-09T05:58:04.138571023Z: minutes after last scaling\\\"=123.2189739776 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=1\"
2022-04-09T05:58:04.138675928Z: vpa recommends changes?\\\"=false\"
2022-04-09T05:58:34.263609886Z: minutes after last scaling\\\"=123.7210577163 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=100\"
2022-04-09T05:58:34.263735055Z: Scaling down\\\"=\\\"memory\\\" \\\"hvpa\\\"=\\\"shoot-garden-aws-us1/kube-apiserver\\\"\"
2022-04-09T05:58:34.263787984Z: vpa recommends changes?\\\"=true\"
2022-04-09T05:58:34.340543031Z: Operation cannot be fulfilled on deployments.apps \\\"kube-apiserver\\\": the object has been modified; please apply your changes to the latest version and try again\\\" \\\"controller\\\"=\\\"hvpa\\\" \\\"name\\\"=\\\"kube-apiserver\\\" \\\"namespace\\\"=\\\"shoot-garden-aws-us1\\\" \\\"reconcilerGroup\\\"=\\\"autoscaling.k8s.io\\\" \\\"reconcilerKind\\\"=\\\"Hvpa\\\" \"
2022-04-09T05:58:35.382916927Z: minutes after last scaling\\\"=123.73971377975 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=100\"
2022-04-09T05:58:35.383044004Z: Scaling down\\\"=\\\"memory\\\" \\\"hvpa\\\"=\\\"shoot-garden-aws-us1/kube-apiserver\\\"\"
2022-04-09T05:58:35.383102893Z: vpa recommends changes?\\\"=true\"
2022-04-09T05:58:35.611365079Z: minutes after last scaling\\\"=0.010185814083333333 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=100\"
2022-04-09T05:58:35.611531019Z: vpa recommends changes?\\\"=false\"
2022-04-09T05:58:35.634959936Z: minutes after last scaling\\\"=0.010581090133333334 \\\"target cpu\\\"=\\\"3908m\\\" \\\"target mem\\\"=\\\"11838448275\\\" \\\"vpaWeight\\\"=100\"
From our aws-us3 seed:
2022-04-09T06:02:43.005808115Z: minutes after last scaling\\\"=4.15009545415 \\\"target cpu\\\"=\\\"4557m\\\" \\\"target mem\\\"=\\\"17591045493\\\" \\\"vpaWeight\\\"=100\"
2022-04-09T06:02:43.005888938Z: vpa recommends changes?\\\"=false\"
2022-04-09T06:02:54.677004098Z: minutes after last scaling\\\"=4.3446153337 \\\"target cpu\\\"=\\\"4557m\\\" \\\"target mem\\\"=\\\"17591045493\\\" \\\"vpaWeight\\\"=100\"
2022-04-09T06:02:54.677201032Z: Scaling up\\\"=\\\"CPU\\\" \\\"hvpa\\\"=\\\"shoot--garden--aws-us3/kube-apiserver\\\"\"
2022-04-09T06:02:54.677248001Z: vpa recommends changes?\\\"=true\"
2022-04-09T06:02:54.815318107Z: minutes after last scaling\\\"=0.013587729916666666 \\\"target cpu\\\"=\\\"4557m\\\" \\\"target mem\\\"=\\\"17591045493\\\" \\\"vpaWeight\\\"=100\"
2022-04-09T06:02:54.815413951Z: vpa recommends changes?\\\"=false\"
2022-04-09T06:02:54.861814975Z: minutes after last scaling\\\"=0.014362126666666667 \\\"target cpu\\\"=\\\"4557m\\\" \\\"target mem\\\"=\\\"17591045493\\\" \\\"vpaWeight\\\"=100\"
Describe the bug:
While trying to understand the HVPA behaviour, I noticed bogus scale up/down cpu/memory messages that seem unrelated to what is actually hapenning.
Expected behaviour:
Log messages matching prev/next settings for cpu/memory.
How To Reproduce (as minimally and precisely as possible):
n/a
Logs:
From our
aws-us1seed:From our
aws-us3seed: