diff --git a/resources/opentelemetry-jaeger-rbac-workaround.yaml b/resources/opentelemetry-jaeger-rbac-workaround.yaml
new file mode 100644
index 0000000..0d781aa
--- /dev/null
+++ b/resources/opentelemetry-jaeger-rbac-workaround.yaml
@@ -0,0 +1,11 @@
+# This is a 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 https://github.com/jaegertracing/helm-charts/issues/549
+rules:
+  - apiGroups:
+      - networking.k8s.io
+    resources:
+      - ingressclasses
+    verbs:
+      - get
+      - list
diff --git a/tests/opentelemetry-tests.bats b/tests/opentelemetry-tests.bats
index 4f2768c..6e87f0f 100644
--- a/tests/opentelemetry-tests.bats
+++ b/tests/opentelemetry-tests.bats
@@ -27,6 +27,10 @@ setup() {
     helm upgrade -i --wait jaeger-operator jaegertracing/jaeger-operator \
         -n jaeger --create-namespace \
         --set rbac.clusterRole=true
+
+    # workaround for https://github.com/jaegertracing/helm-charts/issues/549
+    kubectl patch clusterrole jaeger-operator --patch "$(cat opentelemetry-jaeger-rbac-workaround.yaml)"
+
     kubectl apply -f $RESOURCES_DIR/opentelemetry-jaeger.yaml
     wait_pods -n jaeger