Skip to content

[Bug]: new helm chart: userconfig is not optional #668

@jgournet

Description

@jgournet

What happened?

When using allinone.enabled=false, and no userconfig in values, the collector and query pods still have a configmap mount pointing to user-config, which does not exist, so they fail.

Steps to reproduce

disable allinone
enable query

Expected behavior

the configmap map should only be done if .Values.userconfig exists

Relevant log output

Screenshot

No response

Additional context

maybe the configmap could be called "jaeger-user-config", to avoid potential issues with other applications ?

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions