Discussing the Use and Modification of Helm Charts
TLDR Shivanshu discussed chart's hardcoded feature and raised a case about missing "otelCollector.image", which Srikanth and Steve clarified can be altered, leading to the creation of a related Github issue by Shivanshu.
1
1Aug 14, 2023 (1 month ago)
Shivanshu
01:45 PMeg look at https://github.com/SigNoz/charts/blob/main/charts/signoz/templates/otel-collector/deployment.yaml#L76 and the value is coming from https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml#L1091-L1095, similarly https://github.com/SigNoz/charts/blob/main/charts/clickhouse/values.yaml#L160
And the same thing is happening for all the other components.
BUT this serves the purpose, since, once the helm charts are rendered, it creates the k8s objects and the images are pulled from respective registries. (docker.io/signoz/signoz-otel-collector, docker.io/clickhouse/clickhouse-server, etc)
Even if we modify the charts to default to global registry (if set) you won't be able to use
--set global.image.registry="<http://myregistry.com|myregistry.com>" until unless you have a copy of all the images in the specified global registry (<http://myregistry.com|myregistry.com> in this case)Note:
--set global.image.registry="<http://myregistry.com|myregistry.com>" is for performing a pull operation not push
Srikanth
01:55 PM> no, the current helm charts are pretty much hardcoded.
What Steve said works. The “hardcoded” values are not hardcoded but default. The registry name can always be overrided by
--set global.imageRegistry=... .Shivanshu
02:00 PM> I trying to change de registry of all containers using helm with the parameter:
--set global.image.registry="<http://myregistry.com|myregistry.com>" AFAIU, here the ask is if the registry can be changed for
all containers, but the answer is no, the rendered deployments are not referring to global.image.registry in values.yamlShivanshu
02:07 PMShivanshu
02:11 PMShivanshu
02:13 PM_helpers.tpl does not contain a global default for .Values.otelCollector.imageShivanshu
02:14 PMShivanshu
02:14 PMotelCollector.image is the missing case, right?Srikanth
02:16 PMShivanshu
02:16 PM1Srikanth
02:22 PM1
Steve
06:16 PMSteve
06:17 PM{{- $registryName := default .Values.otelCollector.image.registry .Values.global.imageRegistry -}}
{{- $repositoryName := .Values.otelCollector.image.repository -}}
{{- $tag := .Values.otelCollector.image.tag | toString -}}
{{- if $registryName -}}
{{- printf "%s/%s:%s" $registryName $repositoryName $tag -}}
{{- else -}}
{{- printf "%s:%s" $repositoryName $tag -}}
{{- end -}}
{{- end -}}
SigNoz Community
Indexed 825 threads (61% resolved)
Similar Threads
Extracting Custom Fields as Attributes from Log in SigNoz
Harald wants to have custom fields from their body parsed as attributes in the SigNoz logger. They have tried implementing suggestions from nitya-signoz and Prashant, but the issue remains unsolved due to a potential race condition encountered while executing the code. They have provided a full example using Kind for further assistance.
4Error Upgrading Chart Version in Kubernetes Environment
Manikandan encountered an error when upgrading to a different chart version. Srikanth helps correct the mistake by suggesting to pull the new releases and upgrade.
SigNoz Deployment Issue in Docker Swarm with NFS Share
sati encounters issues with setting up SigNoz in docker-swarm with an NFS share resulting in otel-collector crash and inaccessible GUI. Nick experienced a similar problem and shared a workaround.
SigNoz Production Feedback and Improvement Suggestions
Users shared their SigNoz experiences and feedback. Issues mentioned include memory consumption, UI/UX improvements, connection difficulties, and automation limitations.
8Issues with SigNoz Setup and Data Persistence in AKS
Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.