-
Notifications
You must be signed in to change notification settings - Fork 347
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
[Bug]: jaeger query oauth2-proxy sidecar issues with config #523
Comments
This is correct. We got it to work using this modification to the values.yaml, a separate config of our own, and another template in an wrapper chart where we have it set up to use keycloak at a and jaeger at a path "https:\subdomain.domain\jaeger" I am only adding all of this in case someone doing an update wants to add a few new features along with the fix.
jaeger-tracing\templates\configmap.yaml
jaeger-tracing\config\jaegerConf.yaml
|
What happened?
The oauth2-proxy sidecar doesn't work out of the box with the configmap volume mount.
It needs this -
args:
- --config=/etc/oauth2-proxy/oauth2-proxy.cfg
Steps to reproduce
Enable the Oauth proxy and you get the error.
query:
oAuthSidecar:
enabled: true
Expected behavior
The config should be passed to the config arguments of oauth-proxy container image.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
v1.51.0
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: