Skip to content
This repository was archived by the owner on May 17, 2024. It is now read-only.
This repository was archived by the owner on May 17, 2024. It is now read-only.

ClusterRole does not allow adding header when using --extra-user-header-client-ip #180

Description

@justinas-b

When using --extra-user-header-client-ip argument kube-oidc-proxy is unable to impersonate resource userextras/remote-client-ip with following error:

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "userextras.authentication.k8s.io \"10.251.176.235:50924\" is forbidden: User \"system:serviceaccount:kube-oidc-proxy:kube-oidc-proxy\" cannot impersonate resource \"userextras/remote-client-ip\" in API group \"authentication.k8s.io\" at the cluster scope",
  "reason": "Forbidden",
  "details": {
    "name": "10.251.176.235:50924",
    "group": "authentication.k8s.io",
    "kind": "userextras"
  },
  "code": 403
}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions