Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: failed to list v1.IngressClass is forbidden for apigroup networking.k8s.io #593

Closed
surajnmandhare opened this issue Aug 6, 2024 · 1 comment · Fixed by #592
Closed
Labels
bug Something isn't working

Comments

@surajnmandhare
Copy link

What happened?

eflector.go:147] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:229: Failed to watch *v1.IngressClass: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:jaeger-operator:jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope

Steps to reproduce

Remove the Jaeger instance
Try to re-add it

Expected behavior

Should not complain about permission

Relevant log output

No response

Screenshot

No response

Additional context

  • verbs:
    • create
    • delete
    • get
    • list
    • patch
    • update
    • watch
      apiGroups:
    • networking.k8s.io
      resources:
    • ingresses
    • ingressclasses

Jaeger backend version

NAME CHART VERSION APP VERSION DESCRIPTION jaeger/jaeger-operator 2.55.0 1.57.0 jaeger-operator Helm chart for Kubernetes

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

No response

@surajnmandhare surajnmandhare added the bug Something isn't working label Aug 6, 2024
@kravciak
Copy link
Contributor

kravciak commented Aug 6, 2024

PR with the fix already in the queue #592 ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants