Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow JAEGER_AGENT_PORT env on default Jaeger configuration #397

Merged
merged 2 commits into from
Jan 20, 2019

Conversation

masroorhasan
Copy link
Contributor

@masroorhasan masroorhasan commented Jan 20, 2019

For: #396
Allows JAEGER_AGENT_PORT to be set on deployment manifest to expose specific Jaeger agent port.

@masroorhasan
Copy link
Contributor Author

masroorhasan commented Jan 20, 2019

Now that I'm thinking about it more, exposing other Jaeger config params like service name, sampler type/param via environment variable seems it would further improve flexibility. I could add it part of this PR, thoughts @cliveseldon ?

@ukclivecox ukclivecox merged commit e9479a9 into SeldonIO:master Jan 20, 2019
@ukclivecox
Copy link
Contributor

Thanks!

@masroorhasan masroorhasan deleted the masroor/jaeger-port branch January 20, 2019 20:31
agrski pushed a commit that referenced this pull request Dec 2, 2022
* initial mtls scheduler server commit

* rewrite tls with renew and secret and folder handlers

* scheduler mtls

* add TLS to hodometer

* add docs

* cli docs

* lint

* lint

* test fix lint

* remove use of ioutil

* hodometer lint

* fix components lint

* increase timeout on lint

* make lint version same

* review comments

* ignore cover.out
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.

2 participants