autoscaler: Make cluster-autoscaler log info logs to stdout and errors to stderr

Hi, I’m using cluster-autoscaler with EKS with these args

    spec:
      containers:
      - command:
        - ./cluster-autoscaler
        - --cloud-provider=aws
        - --namespace=infra
        - --node-group-auto-discovery=asg:tag=k8s.io/cluster-autoscaler/enabled,k8s.io/cluster-autoscaler/production
        - --logtostderr=true
        - --stderrthreshold=ERROR
        - --v=4

I want to to log everything with severity < ERROR to stdout, >= ERROR to stderr, as is common practice with most containerized workloads.

By default cluster-autoscaler is logging everything on stderr (even warning, info, debug logs) using the flag --logtostderr=true.

How do I set it up for the desired logging? Is it documented anywhere? Is is using the google/glog library?

Thanks!

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 23
  • Comments: 18 (1 by maintainers)

Most upvoted comments

Was this ever fixed? Cluster-autoscaler is still highly spammy, and it’s hard to find legitimate scaling events amidst the noise.

/remove-lifecycle stale If this isn’t resolved yet, i’ll bump it up - this would be very, very helpful. Our CA is configured like this: logtostderr: true stderrthreshold: ERROR v: 4 and we’re getting ~100k logs per day.

/remove-lifecycle stale

This is still a valid issue IMO

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

/remove-lifecycle stale

This would be a helpful feature.

I’m assuming OP meant:

I want to to log everything with severity < ERROR to stdout, >= ERROR to ~stdout~ stderr, as is common practice with most containerized workloads.