Skip to content

docs : fix README config key mismatch (userconfig) + sync oauth2-proxy version - #781

Open
H3xKatana wants to merge 1 commit into
jaegertracing:mainfrom
H3xKatana:fix/jaeger-readme-userconfig
Open

H3xKatana wants to merge 1 commit into
jaegertracing:mainfrom
H3xKatana:fix/jaeger-readme-userconfig

Conversation

@H3xKatana

Copy link
Copy Markdown

Refs #779. README.md documented a config: key at L12/L133/L225-228 that templates never read (only .Values.userconfig is used — see jaeger-user-config.yaml:1, jaeger-deploy.yaml:55,112,179, values.yaml:69). Following the README verbatim silently no-ops. Also fixed a stale comment in values.yaml:325, synced README's documented oauth2-proxy version to the real default in values.yaml (v7.15.4), and bumped the chart version per the immutability rule in CONTRIBUTING.md. DCO signed. Lint passes, templates render (default + both ci values files).

…proxy version

Templates only read .Values.userconfig; README referenced a
non-existent 'config' key in 3 places, which silently no-ops any
override a user follows verbatim. Also synced the documented
oauth2-proxy version to match values.yaml's actual default (v7.15.4).

Refs jaegertracing#779

Signed-off-by: 0xkatana <m_kara@estin.dz>
@H3xKatana H3xKatana changed the title [jaeger] Fix README config key mismatch (userconfig) + sync oauth2-proxy version docs : fix README config key mismatch (userconfig) + sync oauth2-proxy version Sep 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant