29 Commits (40ed217620bc340ce521c02c99a7000458b652fa)

Author	SHA1	Message	Date
J Stickler	6a473a8407	[Docs] Adding context to Istio installation. (#8248)	2 years ago
gyrofx	ee31c24044	Helm: Add initContainers to write, backend, singleBinary templates (#8236)	2 years ago
Jack Baldry	a6047e9770	Remove template alias from Helm chart reference (#8213) ... With its inclusion, the page tries to redirect https://grafana.com/docs/writers-toolkit/latest/templates/reference-template/ to https://grafana.com/docs/loki/latest/installation/helm/reference/ Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Signed-off-by: Jack Baldry <jack.baldry@grafana.com>	2 years ago
nervo	7aa596752d	Helm - Loki: Introduce runtimeConfig (#8179)	2 years ago
Christian Haudum	d97aaca089	[docs] Clarify for what version the Helm chart docs are applicable (#8172) ... **What this PR does / why we need it**: The docs and reference of the Helm chart in the documentation is only applicable for the Loki Helm chart `>= 3.0` and therefore does not apply to the `grafana/loki-stack` chart, which depends on the Loki Helm chart `^2.15.2` ([requirements.yaml](https://github.com/grafana/helm-charts/blob/main/charts/loki-stack/requirements.yaml#L5)). Also added a headline to the "Install Loki using Helm" index page, because it looks awkward without, see screenshot.  **Which issue(s) this PR fixes**: Fixes: #8152 Signed-off-by: Christian Haudum <christian.haudum@gmail.com>	2 years ago
Prabuddha Chakraborty	20627ad000	Helm: Add ingester config in helm values (#7733) ... **What this PR does / why we need it**: Allow configuring ingester config from helm values: https://grafana.com/docs/loki/latest/configuration/#ingester We wanted to change the default chunk_encoding, which right now not possible in the current values template. Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com>	2 years ago
TAY TS	94ee5a2930	Helm chart: Add enableServiceLinks (#7129) ... **What this PR does / why we need it**: This is to allow disable `enableServiceLinks` so that the service environments are not injected into the pods where in my scenario Loki is deployed in the same namespace as the Knative services resulted the Loki pod unable to start up due to too many service environment being injected. Reference issue for pod unable to startup due to too many services: https://github.com/kubernetes/kubernetes/issues/84539#issue-514261281 Co-authored-by: Trevor Whitney <trevorjwhitney@gmail.com>	2 years ago
openbob	af93f4a11e	Helm: Add Table Manager support to Loki helm chart (#8098) ... The Table Manager is a Loki component which takes care of creating a periodic table before its time period begins, and deleting it once its data time range exceeds the retention period. This PR is to add Table Manager support to the loki helm chart deployment as the current chart is based on the deprecated loki-simple-scalable chart that did not support Table Manager. Fixes #<6830>	2 years ago
Trevor Whitney	eb39e2645f	[helm] allow provisioned tokens to be created in different namespaces (#8081) ... **What this PR does / why we need it**: _Note_: This PR bumps the chart to 4.0, so it includes a few other breaking changes we've been waiting to make. The new helm chart has a few different ways to create tokens when running in enterprise mode: * The tokengen job creates the initial admin token * The provisioner job creates the self-monitoring tenant if enabled * The provisioner job can also create additional tenants if configured The problem with these jobs is they put the generated read/write tokens for these tenants in secrets in the same namespace as the loki deploiyment. This is problematic if you need these tokens for a specific application, for example a Grafana datasource, that is deployed in a separate namespace. This PR introduces two breaking changes, one of which is breaking as it significantly changes how both the self monitoring and additional tenants are configured. First it adds the value `enterprise.adminToken.additionalNamespaces` and moves `enterprise.adminTokenSecret` to `enterprise.adminToken.secret`. If `additionalNamespaces` are included, additional secrets containing the GEL admin token are created in those namespaces as well as the release namespace. Second, it changes the structure of defining a tenant from just a string name, to an object containing a `name` and `secretNamespace` field. The `secretNamespace` is the namespace the secret containing that tenants token(s) will be placed in. In the case of the self-monitoring token, a secret will still be created in the default namespace in addition to the `secretNamespace` specified as that token is required by multiple components.	2 years ago
Nils	e4fbd3c949	Loki: Add support for Azure Workload Identity authentication (#7540)	2 years ago
Jan-Otto Kröpke	59030db186	Add toggle for persistence disk in single-binary mode (#7778)	2 years ago
Trevor Whitney	712bfdd0e0	[helm] add third scalable target `backend` (#7920) ... **What this PR does / why we need it**: Adds the new 3rd scalable deployment mode target (backend) to the helm chart. This new target was added in #7650	2 years ago
MrWong99	380cabaf8c	Fixed typo in Helm values docs (#8075)	2 years ago
Nils	c474f265a7	Add config for optional pod labels (#7594)	2 years ago
Xinbin Huang	7524c4b3dc	[Helm] Add the ability to add extraObjects (#8004) ... **What this PR does / why we need it**: Add the ability to create extraObjects in helm chart. This'll allow users to inject a configmap of loki rules or secrets for object storages. Also, the `extraObjects` is also a common fields for helm charts (i.e. https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml#L1148)	2 years ago
Guillaume Durand	55733561f7	[helm] Add a flag to enable/disable persistentVolumeClaimRetentionPolicy feature (#7640) ... **What this PR does / why we need it**: add a flag to enable/disable persistentVolumeClaimRetentionPolicy feature which is available since kubernetes 1.23 but in alpha (StatefulSetAutoDeletePVC) and disabled by default on most cloud provider I've set the flag to true by default, to not change the actual behavior **Which issue(s) this PR fixes**: Fixes #7249	2 years ago
Quentin Plessis	fde44609c0	[Helm] Add the ability to specify container lifecycle (#8010) ... **What this PR does / why we need it**: Add the ability to specify container lifecycle in helm chart. This is useful when pods are served by a load balancer that needs time to deregister terminating pods, as we can setup a preStop hook to wait a bit before terminating the container. Example: ```yaml gateway: lifecycle: preStop: exec: command: ["/bin/sh", "-c", "sleep 30"] ``` **Which issue(s) this PR fixes**: None **Special notes for your reviewer**: None **Checklist** - [x] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	2 years ago
Tobias Wolf	79e0d96978	Helm: Decouple the Canary from self-monitoring (#7757) ... **What this PR does / why we need it**: The Canary has no dependency on the Grafana Agent-based self-monitoring. This PR decouples that dependency, allowing the canary to be deployed with the other self-monitoring features. **Which issue(s) this PR fixes**: Fixes #7364	2 years ago
Trevor Whitney	652e216a85	[helm] Bump helm Loki and GEL version (#7760) ... **What this PR does / why we need it**: Bumps Loki to 2.7.0 and GEL to 1.6.0 in the helm chart.	3 years ago
Anders Bennedsgaard	b5563cee08	[Helm] Remove unused value and set default values explicitly (#7576) ... **What this PR does / why we need it**: `monitoring.alerts` are not used in the Loki Helm chart. This removes it. Furthermore, some values are referenced in the templates, but not used in the values file. This adds the default values. **Which issue(s) this PR fixes**: Fixes #7575 **Special notes for your reviewer**: https://github.com/AndersBennedsgaard/loki/blob/main/production/helm/loki/templates/single-binary/pdb.yaml#L15 should probably also be updated since `podDisruptionBudget` is not referenced in the values file. However, I am unsure what default values should be used. https://github.com/AndersBennedsgaard/loki/blob/main/production/helm/loki/templates/networkpolicy.yaml#L124 should probably also be updated since the `loki.rulerSelectorLabels` is not a valid helper function. However, I am unsure which selector labels to use. Especially since it seems like `ruler` is not used. Perhaps any reference to `ruler` should be removed? **Checklist** - [x] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Jan-Otto Kröpke	5dc60567da	[Helm] Add support for azure blob storage (#7500) ... **What this PR does / why we need it**: Support Azure Blob Storage in helm chart. See https://grafana.com/docs/loki/latest/storage/#azure-storage-account-1 **Which issue(s) this PR fixes**: **Special notes for your reviewer**: **Checklist** - [ ] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [ ] Tests updated - [x] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Signed-off-by: Jan-Otto Kröpke <jok@cloudeteer.de>	3 years ago
Teddy Andrieux	217a914f98	helm/loki: Allow to override default loki `target` (#7791) ... **What this PR does / why we need it**: Add the ability to change the Loki `target` argument. E.g. one might want to use the single-binary which has target `all` but also the `table-manager` which is not part of it. So one can override the target with `all,table-manager`. **Which issue(s) this PR fixes**: Fixes #7788 **Special notes for your reviewer**: **Checklist** - [x] Reviewed the `CONTRIBUTING.md` guide - [x] `CHANGELOG.md` updated	3 years ago
Trevor Whitney	ea4a764143	[helm] Fix incorrect ingress paths when using single binary deployment (#7530) ... **What this PR does / why we need it**: The helm ingress template was copied over from the simple scalable chart and does not work when deploying the chart in single binary configuration. This fixes that by adding a set of single binary routes, and conditionally configuring the ingress resource based on deployment type. **Which issue(s) this PR fixes**: Fixes #7080 **Special notes for your reviewer**: **Checklist** - [ ] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Teddy Andrieux	220770c693	helm/loki: Allow to provide selector for Loki persistence volume (#7743)	3 years ago
Karsten Jeschkies	54320e827c	Correct Helm documentation aliases. (#7537) ... **What this PR does / why we need it**: #7034 introduced a regression in the documentation. This changes corrects the aliases of the Helm documentation pages. **Checklist** - [ ] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Jasper	706c22e9e4	Loki: Add querier config to loki helm (#7627) ... add the ability to update querier config using `values.yaml` file	3 years ago
Max Vorobev	e537cb52d3	[Helm] fix typos in parameter descriptions (#7527) ... **What this PR does / why we need it**: Fixes typos in metrics-related Helm chart parameter descriptions. **Which issue(s) this PR fixes**: Fixes #<issue number> **Special notes for your reviewer**: **Checklist** - [x] Reviewed the `CONTRIBUTING.md` guide - [x] Documentation added - [x] Tests updated - [x] `CHANGELOG.md` updated - [x] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md`	3 years ago
Jan-Otto Kröpke	9e300baf89	[Helm] Add toggle for MetricsInstance (#7525) ... Signed-off-by: Jan-Otto Kröpke <jok@cloudeteer.de> **What this PR does / why we need it**: Chart version 3.3.0 introduced a new MetricsInstance CR. The only way to disable the MetricsInstance is `--set loki.monitoring.serviceMonitor.metricsInstance=null`, but this raises helm warning... ``` coalesce.go:220: warning: cannot overwrite table with non table for loki.monitoring.serviceMonitor.metricsInstance (map[annotations:map[] labels:map[] remoteWrite:<nil>]) coalesce.go:220: warning: cannot overwrite table with non table for loki.monitoring.serviceMonitor.metricsInstance (map[annotations:map[] labels:map[] remoteWrite:<nil>]) coalesce.go:220: warning: cannot overwrite table with non table for loki.monitoring.serviceMonitor.metricsInstance (map[annotations:map[] labels:map[] remoteWrite:<nil>]) ``` **Checklist** - [ ] Reviewed the `CONTRIBUTING.md` guide - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` Signed-off-by: Jan-Otto Kröpke <jok@cloudeteer.de>	3 years ago
Karsten Jeschkies	b16ad8cb38	Document new Helm Charts (#7034) ... **What this PR does / why we need it**: This change describes various Helm related tasks such as installing Loki and configuring meta monitoring. It also explains different concepts related to the new Helm chart and provides a reference of the new Helm values file. **Which issue(s) this PR fixes**: Fixes #7035	3 years ago