helm-charts | A curated set of Helm charts brought to you by WESEEK , Inc

As Nick Bailey pointed out in the comments, this is a stylistic change, not a structural one. That is, the data is the same, it's just presented differently.

Now, as for what that style is, YAML has two styles of presenting data structures:

• Block style: Each key/value starts on a new line, and both lists and dictionaries (mappings) are started and stopped via indentation. This is usually the preferred style, as it is more human-readable.

• Flow style: Lists/mappings are started and ended by brackets, and multiple key/values are separated by commas, as in JSON. Line breaks aren't required between key/value pairs, but also not disallowed. This format is more commonly used for smaller, simpler data structures, especially on a single line, since it can save space.

The original YAML you've shown is one key/value pair within a larger block-style mapping, but the value itself isn't block style; it's just flow style with extra line breaks added. I think you probably want this instead, fully in block style:

Promtail should be configured to replace the string with the replace stage.

Here is a sample config that removes the stdout F part of the log for all logs coming from the namespace ingress.

I'm able to use kubectl top on pods that have linkerd injected:

It's not enough to simply install them, you need to integrate prometheus with thanos.

Below I'll describe all steps you need to perform to get the result.

First short theory. The most common approach to integrate them is to use thanos sidecar container for prometheus pod. You can read more here.

How this is done:

(considering that installation is clean, it can be easily deleted and reinstalled from the scratch).

1. Get thanos sidecar added to the prometheus pod.

Pull kube-prometheus-stack chart:

an operator pod acts as a controller that listens to events regarding specific custom resources. if you only deploy the operator, you have to seperately deploy the custom resource you wish to be created.

with the prometeus-operator, that would be a custom resource of kind "prometheus". if the helm chart you choose is capable to also deploy this (or not) should be indicated in the charts values.yaml and documented on their github page.

you can also use the examples from the prometheus-operator repo to create prometheus instances. check out these files to do so: https://github.com/prometheus-operator/prometheus-operator/tree/main/example/rbac/prometheus

Secret ... is invalid: data: Too long: must have at most 1048576 bytes

This is a well known limitation of Kubernetes secrets (version 1.23 at the moment). The official k8s documentation says:

Individual secrets are limited to 1MiB in size. This is to discourage creation of very large secrets which would exhaust the API server and kubelet memory. However, creation of many smaller secrets could also exhaust memory. More comprehensive limits on memory usage due to secrets is a planned feature.

So, first of all, check if some unnecessary files/dirs are stored in your chart directories and remove them. I am sure you have already removed all unnecessary files.

Using such a storage backend is particularly useful if your release information weighs more than 1MB (in which case, it can't be stored in Secrets because of internal limits in Kubernetes).

To enable the SQL backend, you'll need to deploy a SQL database and set the environmental variable HELM_DRIVER to sql. The DB details are set with the environmental variable HELM_DRIVER_SQL_CONNECTION_STRING.

You can set it in a shell as follows:

Enable persistence if you want to make it stateful. However I did not see an option to make Grafana a statefulset in the chart you mentioned.

Usually you will see persistence enable option if the corresponding Helm chart support it. For example: you can enable persistence in this grafana helm chart. You may generate template out of it and make use of it in your repo.

You can use the k8sutil repo, see the apply example:

This is documented in Helm website

Overriding Values from a Parent Chart

so in your top level chart's values.yaml, use construct like this: