[Bug]: Bitnami Common Chart no longer has the supportsIngressClassname Template

[maynardflies]

What happened?

Jaeger v2 charts pin bitnami/common chart to 2.x.x, and in the AllInOne (and in v2 branch, all) ingress templates, use the supportsIngressClassName template when ingress is enabled, but since common chart 2.31.1 that template was removed. Since this check is only to validate that the cluster is >1.18, and in recent versions of the common chart it was hardcoded to "true", it may be appropriate to just remove this check. If not, then pulling it into this chart's templates would work too.

Steps to reproduce

1. Pull chart into clean environment
2. configure it to use AllInOne and enable ingress
3. deploy to cluster

Expected behavior

Deploy happens cleanly

Relevant log output

Error: template: jaeger/templates/allinone-ing.yaml:2:44: executing \"jaeger/templates/allinone-ing.yaml\" at <include \"common.ingress.supportsIngressClassname\" .>: error calling include: template: no template \"common.ingress.supportsIngressClassname\" associated with template \"gotpl\"

Screenshot

No response

Additional context

No response

Jaeger backend version

Chart version 4.1.5 (problem exists in all >=4.x charts)

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs