Loki Helm Chart does not include the release name in the kubernetes objects

[rkdutta]

Describe the bug
When loki helm chart is installed some of the component name does not include the release name. Specially the run-time configmap. Its possible to use nameoverride. But I was expecitng some sync in all installed objects.
Following is one installation where release name is my-loki.

loki-canary
ServiceAccount
---
loki
ServiceAccount
---
loki
ConfigMap
---
my-loki-gateway
ConfigMap
---
loki-runtime
ConfigMap
---
my-loki-clusterrole
ClusterRole
---
my-loki-clusterrolebinding
ClusterRoleBinding
---
my-loki-chunks-cache
Service
---
my-loki-gateway
Service
---
loki-canary
Service
---
my-loki-results-cache
Service
---
loki-memberlist
Service
---
loki-canary
DaemonSet
---
my-loki-gateway
Deployment
---
my-loki-chunks-cache
StatefulSet
---
my-loki-results-cache
StatefulSet
---
loki-helm-test
Pod

To Reproduce
Steps to reproduce the behavior:

1. Execute the following command:

helm template my-loki grafana/loki --version 6.33.0 -f helm/argos/values.yaml  --set loki.useTestSchema=true --set loki.runtimeConfig.overrides.tenant1.retention_period=24h --set loki.storage.bucketNames.chunks=common-chunks --set deploymentMode=distributed| yq '.'  | yq '.metadata.name,.kind'

Expected behavior
All installed component should include the release name by deafult.

Environment:

• Infrastructure: Kubernetes
• Deployment tool: helm

[jkroepke]

@JStickler @Jayclifford345 It would be great to know if there is some historic reason for not using Release.Name in some kubernetes objects like loki-memberlist.

But I guess this issue might be fixed in the next major version of the loki helm chart.

[rkdutta]

any updates on this?

[ki3lich]

Renaming the serviceAccount and other components requires using nameOverride. Try adding argument --set nameOverride=my-loki.