Mistaken auth header name about go HOT 6 CLOSED

I am getting the same error. Unfortunately, even the workaround provided above doesn't seem to work for me.

Error Reading abc-svc-config-map ConfigMap Status: 403 Forbidden, Body: {"kind":"Status","apiVersion":"v1", "metadata":{},"status":"Failure","message":"configmaps \"abc-svc-config-map\" is forbidden: User \"system:serviceaccount:test:api-access-sa\" cannot get resource \"configmaps\" in API group \"\" at the cluster scope","reason":"Forbidden","details":{"name":"abc-svc-config-map","kind":"configmaps"},"code":403}

am I missing something ? Is there any fix in progress ?

Thanks,

-SR

from go.

I found issue why the above workaround was not working. The ClusterRoleBinding was not applied to the role in the namespace the pod was running. Now that I have added, the workaround is working and I am able to reach the API Server.

from go.

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

from go.

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

from go.

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

from go.

@fejta-bot: Closing this issue.

from go.