You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
apiGroups:
resources:
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
The text was updated successfully, but these errors were encountered: