fix(helm): fix query-frontend and ruler targetPort 'http-metrics' in Service template

[archimeid]

What this PR does / why we need it:

This PR is a fix for Loki Helm Chart.

The templates for query-frontend-headless Service and ruler Service have an issue on "targetPort".

This issue is the same as the one detected for query-scheduler in version 6.6.1.

- name: http-metrics
   port: 3100
   targetPort: http
   protocol: TCP

targetPort is currently http but the port name in Deployment (or StatefulSet) template is http-metrics.

Template for query-frontend deployment

Template for ruler stateful-set

Thus, those Services have no endpoint available for the http-metrics port because of the mismatch.

Setting targetPort to http-metrics has solved the issue.

Which issue(s) this PR fixes:
N/A

Special notes for your reviewer:
N/A

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[CLAassistant]

All committers have signed the CLA.

[DylanGuedes]

could you also fix the ruler and QF?

[archimeid]

could you also fix the ruler and QF?

Done

[DylanGuedes]

thanks, this is fantastic ❤️

• I have changed the PR title to fix the CI
• could you also approve the CLA?

[archimeid]

thanks, this is fantastic ❤️

* I have changed the PR title to fix the CI

* could you also approve the CLA?

Happy if I could help! 👍

I've already approved it several times but it didn't refresh in here.

[DylanGuedes]

could you trigger a recheck by visiting https://cla-assistant.io/check/grafana/loki?pullRequest=13024?

[archimeid]

I did many times but it does not work.

[archimeid]

A fix seems to be merged for the same issue now apparently when trying to resolve conflicts with main branch.

[DylanGuedes]

@archimeid a colleague just pointed out the fact that there are commits from this other account @vpo-cdc, it needs to have a CLA approval from him too

[archimeid]

OMG, you're totally right. I have edited my commit. It was another user I am using at work.
As the issue was resolved for query-scheduler in 6.6.1 but not for query-frontend and ruler, I edited my commit to fix both and bump to 6.6.2.