-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Hi,
I am currently running the reverse proxy on a istio based cluster. I notice that the token expires after an hour.
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}I believe its because of aggressive caching of envoy.
Additionally, having the healthy probe to get the token itself would be a better option, in case if it finds the endpoint dead, it will restart.
Right now I am testing the charts with
podAnnotations:
traffic.sidecar.istio.io/excludeOutboundPorts: "443"Having something like might help (?)
livenessProbe:
httpGet:
path: /openid/v1/jwks
port: httpI am going to wait for some time to see if it helps anymore. I would like to hear any thoughts on this. (BTW i am new to istio, and might be wrong somewhere)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels