fix: Apply workaround for jaeger rbac permissions #109
Conversation
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
force-pushed
the
workaround-jaeger-rbac
branch
from
8acbbea to
f5dcf72
Compare
|
Note, this happens at least for jaeger-operator-2.54.0 chart, yet it does not happen for the chart version we use in docs.kubewarden.io. Hence why I'm only concerned about a workaround for the e2e tests. |
We need to update the docs then. Because in the dependency matrix we state that we support the jaeger operator helm chart appVersion |
|
I thought so, but it seems the chart column is fine. For jaeger-operator it is |
Oh, yeah. That's fine. I've misunderstood what you said. As I said in our quick chat in other channel, I missed the upstream bug that is out of our control. Everything should be fine in our side. So, this is fine and good to go. |
Description
Relates to kubewarden/helm-charts#492
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
Test
Tested locally.
Additional Information
Tradeoff
Potential improvement