Missing cluster permissions in clusterrole

Open Beginner friendly
#8,887 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
kubernetes

Research direction

Start by locating the controller's ClusterRole manifest and compare its rules with the permissions listed under Correction. Reproduce the cross-namespace gateway and EnvoyProxy setup, then verify that TokenReview and SubjectAccessReview calls no longer fail.

Written by the indexing model from the issue text.

Description

stale triage

Description:
"failed to call TokenReview API to verify service acacount jwt"

Repro steps:
create a gateway and envoyproxy in a different namespace to the controller

Environment:
1.7.1

Logs:
See desc.

Correction

    • apiGroups:
  •  - authentication.k8s.io
    
  • resources:
  •  - tokenreviews
    
  • verbs:
  •  - create
    
    • apiGroups:
  •  - authorization.k8s.io
    
  • resources:
  •  - subjectaccessreviews
    
  • verbs:
  •  - create
    
Dominant language
Go
Stars
3k
Forks
868
Avg merge
1d 13h
Merged PRs (30d)
124

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/gateway

All issues in envoyproxy/gateway

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.