We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.14.x (latest stable)
Currently you are able to sidecar the extauth into the gateway proxy with the global.extensions.extAuth.envoySidecar option. For a multi gateway deployment https://docs.solo.io/gloo-edge/latest/installation/advanced_configuration/multi-gw-deployment/ it will side car all gateways with the extauth container.
global.extensions.extAuth.envoySidecar
It would be nice to have the ability to specify which gateway to sidecar the extauth container in multi-gateway deployment.
No response
The text was updated successfully, but these errors were encountered:
Added in https://github.com/solo-io/solo-projects/pull/5503 and will be part of v1.16.0-beta3 when released
Sorry, something went wrong.
davidjumani
No branches or pull requests
Version
1.14.x (latest stable)
Is your feature request related to a problem? Please describe.
Currently you are able to sidecar the extauth into the gateway proxy with the
global.extensions.extAuth.envoySidecar
option. For a multi gateway deployment https://docs.solo.io/gloo-edge/latest/installation/advanced_configuration/multi-gw-deployment/ it will side car all gateways with the extauth container.Describe the solution you'd like
It would be nice to have the ability to specify which gateway to sidecar the extauth container in multi-gateway deployment.
Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: