You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
envoy now supports specifying paths on which we should use JWT validation. We can use this feature to do JWT validation on the non-healthcheck routes. This will allows us to replace the two envoy containers with a single one.
The text was updated successfully, but these errors were encountered:
* Replace two envoy containers with a single one
Use bypass_jwt field to bypass jwt validation for /healthz and
/noiap/whoami routes
Tested by disabling IAP - verified that /healthz and /noiap/whoami work
and other routes return an error - Required JWT token is missing
Fixes#404
* Autoformat iap.libsonnet
yanniszark
added a commit
to arrikto/kubeflow
that referenced
this issue
Nov 1, 2019
)
Remove the metacontroller application from the existing_arrikto
config as it is no longer used.
Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
envoy now supports specifying paths on which we should use JWT validation. We can use this feature to do JWT validation on the non-healthcheck routes. This will allows us to replace the two envoy containers with a single one.
The text was updated successfully, but these errors were encountered: