🌱 hack/observability: Bump Loki, Grafana and promtail charts

[sbueringer]

What this PR does / why we need it:

This PR bumps Loki, Grafana and promtail Helm charts

just for reference, we had to resolve the following issues to unblock this change:

• It aws not possible to deploy the Helm Chart into a specific namespace: [Helm] 3.0.0 Chart does not deploy into .Release.Namespace grafana/loki#7089
• It was not possible to disable the deployment of a ServiceMonitor: New 3.0 helm chart install fails and produces "no matches for kind" grafana/loki#7047 (comment)
• We have to set a OrgID to avoid an auth issue when sending logs to Loki (and then also in the Grafana datasource): server returned HTTP status 401 Unauthorized (401): no org id grafana/loki#7081
  • This can be avoided by setting loki.auth_enabled to false (it's true per default)

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sbueringer]

/remove-lifecycle stale

We should still bump when the chart is fixed

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sbueringer]

/remove-lifecycle stale

Currently trying to improve the Loki Helm chart so we can finally finish this

[sbueringer]

/assign @killianmuldoon @fabriziopandini @ykakarap

I did a quick local test with logs and metrics it seems to be working.

EDIT: Also verified log push now.

Would be great if someone can double check.

[sbueringer]

Btw I think we should continue pinning Helm chart versions. I think it's the only safe thing to do.

[fabriziopandini]

This is great!
/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 4f61636966dab1dc4b71c5087a2aa2a446b62aee

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[johannesfrey]

/area devtools