Error starting container: Unknown flag: --logtostderr

[shpml]

What happened?:
On Aug 12th AEST my prometheus adapter pod was gracefully terminated.

"timestamp": "2022-08-11T17:47:01.987570641Z",
"message": "\"[graceful-termination] shutdown event\" name=\"ShutdownInitiated\""

This resulted in a pod restart and kubernetes pulling the latest image.

"timestamp": "2022-08-11T17:48:01Z",
"message": "Successfully pulled image \"gcr.io/k8s-staging-prometheus-adapter/prometheus-adapter-amd64:master\" in 57.551120744s",

This resulted in a "CrashLoopBackOff" event due to the following error

"timestamp": "2022-08-11T17:48:01.241961584Z",
"textPayload": "unknown flag: --logtostderr",

Unfortunately I did not have monitoring on this cluster so I missed the errors for a number of days :(.
The pod with the issue was deleted on Aug 16th AEST and a new pod successfully started after pulling the latest image

"timestamp": "2022-08-16T12:14:06Z",
"message": "Successfully pulled image \"gcr.io/k8s-staging-prometheus-adapter/prometheus-adapter-amd64:master\" in 7.038956364s"

The container successfully started.

"timestamp": "2022-08-16T12:14:06Z",
"message": "Started container custom-metrics-apiserver",

What did you expect to happen?:
I expected a new pod to start without an error relating to flag logtostderr.

Please provide the prometheus-adapter config:
The config is the default used in deploy/manifests/custom-metrics-apiserver-deployment.yaml

prometheus-adapter/deploy/manifests/custom-metrics-apiserver-deployment.yaml

Line 31 in f23e671

- --config=/etc/adapter/config.yaml

Anything else we need to know?:
I don't think it's still a bug as the latest version is running but it would be good to know what happened.

Environment:

• prometheus-adapter version: gcr.io/k8s-staging-prometheus-adapter/prometheus-adapter-amd64:master
• prometheus version: gke.gcr.io/prometheus-engine/prometheus:v2.35.0-gmp.2-gke.0
• Kubernetes version: v1.21.x-gke and v1.22.10-gke.600
• Cloud provider: GKE

[olivierlemasle]

There was visibly a regression, which was fixed in #524.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.