jaegertracing / jaegertracing/documentation

[operator] Document env vars for overriding Jaeger image sources

Open
#310 3 comments 1 reaction 0 assignees View on GitHub
operator
Dominant language
TypeScript
Stars
84
Forks
192
Avg merge
12h 25m
Merged PRs (30d)
4

Description

This is important when running Jaeger on a self-hosted cluster with no direct access to the Docker Hub.

The support for them was added in jaegertracing/jaeger-operator#21, but neither the documentation nor the deployment YAML indicate they exist and what their names are. I had to look at the source code and read Viper documentation to learn that they should be called JAEGER-ALL-IN-ONE-IMAGE, OPENSHIFT-OAUTH-PROXY-IMAGE etc.

Contributor guide

Open the contributing guide

Research direction

Start by locating the documentation and deployment YAML for the Jaeger operator, then compare them with the existing environment-variable support and the Viper naming rules. Document the image override variable names, and update the deployment YAML so both sources show the available overrides.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.