Closed viccuad closed 3 months ago
viccuad
commented
3 months ago 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.
jvanz
commented
3 months ago 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 >= 1.49 < 2. And the 2.54.0 chart version is valid. The appVersion there is 1.57.0 version
viccuad
commented
3 months ago I thought so, but it seems the chart column is fine. For jaeger-operator it is appVersion >= 1.49 < 2, version example 2.49.0. And the latest jaeger-operator is appVersion1.57.0 (within bounds).
jvanz
commented
3 months ago I thought so, but it seems the chart column is fine. For jaeger-operator it is
appVersion >= 1.49 < 2,version example 2.49.0. And the latest jaeger-operator isappVersion1.57.0(within bounds).
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 https://github.com/kubewarden/helm-charts/issues/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 https://github.com/jaegertracing/helm-charts/issues/549
Test
Tested locally.
Additional Information
Tradeoff
Potential improvement