kube-static-metrics addon-resizer error

[liuwenjiegithub]

ERROR: logging before flag.Parse: I0326 14:44:55.136801 1 pod_nanny.go:81] Watching namespace: kube-system, pod: kube-state-metrics-65f9c6fcdf-gcbrm, container: kube-state-metrics.
ERROR: logging before flag.Parse: I0326 14:44:55.136808 1 pod_nanny.go:82] storage: MISSING, extra_storage: 0Gi
ERROR: logging before flag.Parse: I0326 14:44:55.138236 1 pod_nanny.go:171] Failed to read data from config file "MISSING/NannyConfiguration": open MISSING/NannyConfiguration: no such file or directory, using default parameters
ERROR: logging before flag.Parse: I0326 14:44:55.138294 1 pod_nanny.go:109] cpu: 100m, extra_cpu: 1m, memory: 100Mi, extra_memory: 2Mi
ERROR: logging before flag.Parse: I0326 14:44:55.138315 1 pod_nanny.go:138] Resources: [{Base:{i:{value:100 scale:-3} d:{Dec:} s:100m Format:DecimalSI} ExtraPerNode:{i:{value:1 scale:-3} d:{Dec:} s:1m Format:DecimalSI} Name:cpu} {Base:{i:{value:104857600 scale:0} d:{Dec:} s:100Mi Format:BinarySI} ExtraPerNode:{i:{value:2097152 scale:0} d:{Dec:} s:2Mi Format:BinarySI} Name:memory}]

kubernetes 1.13.3
addon-resizer:1.8.3

[avdhoot]

facing same issue

[avdhoot]

To things work changed version of addon-resizer:1.8.4 & Changed memory(base) arg of addon-resizer container to --memory=500Mi . Not sure that much memory is required by 'kube-state-metrics' are not. Launched kube-state-metrics container is taking around 498Mi Hope it help.

[brancz]

Sounds like we also need to configure a parameter for storage?

[avdhoot]

Memory usage are down.

[brancz]

did you deploy a new version of kube-state-metrics? v1.5.0 had major memory improvements :)

[avdhoot]

Yep. It is 1.5.0. Initial few min it need much more memory.

[brancz]

In that case this is a good graph no? :) the memory improvements worked

[zouyee]

kubernetes/autoscaler#559

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.