Why we still need to specify --requestheader-client-ca-file flag for metrics-server

[fuxiaoting]

Hello,
Is this known issue still valid?

metrics-server/KNOWN_ISSUES.md

Line 251 in a6a0ea3

To fix this problem you need to provide kube-apiserver proxy-client CA to Metrics Server under `--requestheader-client-ca-file` flag. You can read more about this flag in [Authenticating Proxy](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#authenticating-proxy)

We have set this flag in kube-apiserver k8s-args, and there is a configmap extension-apiserver-authentication created under namespace kube-system.
Why metrics-server apiservice could not get this setting from configmap extension-apiserver-authentication ?

[dashpole]

/assign @yangjunmyfm192085
/triage accepted

[yangjunmyfm192085]

yeah, metrics-server apiservice could get this setting from configmap extension-apiserver-authentication.
I'm not sure about the scene at that time /cc @QianChenglong

[yangjunmyfm192085]

from here
#533

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[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