-
Notifications
You must be signed in to change notification settings - Fork 15
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
not all config parameters are parsed #21
Comments
I wounder how ProxyInjector invokes keycloak-gatekeeper: shouldnt it be through the config.yml file like |
@huegelc is this issue still valid? |
@rasheedamir This is the secret config.yaml for proxyinjector:
and this are the env of the pod:
You see, there are a lot of config options missing/not passed to the proxy pod And here is the annotation of the deployment:
It seems that
|
Hi,
ProxyInjector is a really nice idea so we played around a bit and noticed that not all config parameters are parsed into the container when launching a annotated application.
Here is my ProxyInjector deployment:
the created configmap:
and here the yaml of the deployed application:
as you see there are a lot of config options missing.
Edit:
when deploying the app annotated like this
it works:
The text was updated successfully, but these errors were encountered: