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
Using 120s is a valid workaround. However, in the documentation is stated that "2m" should work (See the example given in Idle Timeout that references to the non-idle timeout)
The text was updated successfully, but these errors were encountered:
What happened?
I am receiving the following event on the Ingress:
What did you expect to happen?
I expected to be able to use "2m" as in "2 minutes" in the annotation
ingress.pomerium.io/timeout
documented hereHow'd it happen?
ingress.pomerium.io/timeout: '2m'
What's your environment like?
docker.io/pomerium/ingress-controller@sha256:f40d7bfeb618f39c9f8190dc21cfc6f53eb046257b1eda848c3585bc6a206e69
(friendly name:docker.io/pomerium/ingress-controller:v0.26.0
)What's your config.yaml?
Configuration is applied using custom resource
Pomerium
What did you see in the logs?
Additional context
Using
120s
is a valid workaround. However, in the documentation is stated that "2m" should work (See the example given in Idle Timeout that references to the non-idle timeout)The text was updated successfully, but these errors were encountered: