-
Notifications
You must be signed in to change notification settings - Fork 347
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 #549
Open
tcpecheanu opened this issue
Apr 3, 2024
· 1 comment
· May be fixed by bouchardmathieu-qc/jaegertracing-helm-charts#1
Open
[Bug]: failed to list v1.IngressClass is forbidden #549
tcpecheanu opened this issue
Apr 3, 2024
· 1 comment
· May be fixed by bouchardmathieu-qc/jaegertracing-helm-charts#1
Labels
bug
Something isn't working
Comments
Related: #544 (comment) |
5 tasks
bouchardmathieu-qc
added a commit
to bouchardmathieu-qc/jaegertracing-helm-charts
that referenced
this issue
May 31, 2024
The updated jaeger-operator is querying the cluster to know informations about ingressclasses. But the role created by the jaeger-operator helm chart doesn't allow get or list on ingressclasses. This change addresses that. Fixes jaegertracing#549 Signed-off-by: Mathieu Bouchard <[email protected]>
viccuad
added a commit
to viccuad/kubewarden-end-to-end-tests
that referenced
this issue
Jul 29, 2024
Apply workaround for the jaeger ClusterRole, that seems to be missing permissions to list ingressclasses. This makes the jaeger operator not reconcile the expected ingress service. See jaegertracing/helm-charts#549 Signed-off-by: Víctor Cuadrado Juan <[email protected]>
viccuad
added a commit
to viccuad/kubewarden-end-to-end-tests
that referenced
this issue
Jul 29, 2024
Apply workaround for the jaeger ClusterRole, that seems to be missing permissions to list ingressclasses. This makes the jaeger operator not reconcile the expected ingress service. See jaegertracing/helm-charts#549 Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When trying to recreate a jaeger instance I'm getting the following error in the operator:
I already have enabled rbac and service account creation.
Steps to reproduce
Expected behavior
Recreate the Jeager instance without doing any manual change.
Relevant log output
Screenshot
No response
Additional context
The fix is very simple, just add the ingressclasses resource access to the jaeger-operator clusterrole under networking.k8s.io, like below
Jaeger backend version
v1.55.0
SDK
No response
Pipeline
No response
Stogage backend
Elasticsearch v8.12.0
Operating system
Linux
Deployment model
Kubernetes v1.27.8
Deployment configs
The text was updated successfully, but these errors were encountered: