[bitnami/jaeger] Add optional Ingress support for Jaeger UI

[aparnams1999]

Description of the change

This change adds optional Ingress support for the Jaeger Query service in the Bitnami Jaeger Helm chart.

Introduces an ingress block in values.yaml to enable configuring hostname, path, ingress class, annotations, and TLS.

Updates the chart templates to conditionally create a Kubernetes Ingress resource targeting the jaeger-query service on port 16686 when ingress is enabled.

Aligns the Jaeger chart with other Bitnami charts that provide native Ingress support, improving deployment automation and ease of use.

Benefits

Simplifies exposing the Jaeger Query UI by allowing users to enable and configure Ingress directly via Helm values.

Eliminates the need for users to manually create and manage separate Ingress resources outside the chart, reducing operational overhead.

Enables consistent and standardized ingress configurations, including support for TLS and annotations for common ingress controllers.

Enhances automation by integrating ingress resource lifecycle with Helm, ensuring Ingress is created, updated, or deleted with the chart.

Brings the Jaeger chart in line with Bitnami’s best practices and other charts that already include native Ingress support.

Possible drawbacks

Not to my knowledge

Applicable issues

• Add optional Ingress support for Jaeger Query #35742

Additional information

Tested with NGINX ingress controller on Kubernetes

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[aparnams1999]

Hi, please let me know if I need to make any changes from my side. I noticed that some pipelines are failing.

[gongomgra]

Hi @aparnams1999. It looks like the deployment is failing with your changes. Can you try to reproduce it?

Not all endpoints are ready after the time out. 1 of 4 failed:
  [name=ing-jaeger-http, ready=false, expectedToBeReady=true, type=INGRESS],

[github-actions]

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

[github-actions]

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.