Update loki-stack and set health_check_targets: false.

[reitermarkus]

Description

Motivation and Context

Fixes openebs/mayastor#1560.

Regression

No.

How Has This Been Tested?

Running with current helm chart and this configuration:

loki-stack:
  promtail:
    config:
      # TODO: Remove once Mayastor chart is updated.
      file: |
        server:
          log_level: {{ .Values.config.logLevel }}
          http_listen_port: {{ .Values.config.serverPort }}
          {{- tpl .Values.config.snippets.extraServerConfigs . | nindent 2 }}

        clients:
          - url: {{ tpl .Values.config.lokiAddress . }}
          {{- with .Values.config.snippets.extraClientConfigs }}
          {{- toYaml . | nindent 2 }}
          {{- end }}

        positions:
          filename: /run/promtail/positions.yaml

        scrape_configs:
          {{- tpl .Values.config.snippets.scrapeConfigs . | nindent 2 }}
          {{- tpl .Values.config.snippets.extraScrapeConfigs . | nindent 2 }}

      snippets:
        extraServerConfigs: |-
          health_check_target: false

The {{- tpl .Values.config.snippets.extraServerConfigs . | nindent 2 }} part is included by default in newer versions of the loki-stack chart.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added unit tests to cover my changes.

[Abhinandan-Purkait]

@reitermarkus You need to remove the . from your commit message for the commit lint.

[tiagolobocastro]

@reitermarkus You need to remove the . from your commit message for the commit lint.

Also lowercase update

[tiagolobocastro]

@reitermarkus, also please regenerate the docs:

./scripts/helm/generate-readme.sh

We need to add this to GHA too I guess, I'll fix this on another PR.

[reitermarkus]

Given #387 is merged, should I still update this PR?

[tiagolobocastro]

Given #387 is merged, should I still update this PR?

Yes please, 387 was merged to the release branch, this is targetting develop

[tiagolobocastro]

@niladrih PTAL and sequence merge whichever way you think is better for the upgrade changes

[niladrih]

bors merge

[bors-openebs-mayastor]

Build succeeded:

• continuous-integration/jenkins/branch