Skip to content
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

Cannot change globalExtAuth timeout #6820

Open
kncesarini opened this issue Dec 18, 2024 · 1 comment
Open

Cannot change globalExtAuth timeout #6820

kncesarini opened this issue Dec 18, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@kncesarini
Copy link

What steps did you take and what happened:

We are experiencing a 200ms timeout on all authorization requests (if they happen to take more than 200ms, which happens on rare occasions), leading to 403 responses.

We have configured global external authentication like this in the configmap (as per https://github.com/projectcontour/contour/blob/main/examples/global-external-auth/03-contour-config.yaml):

apiVersion: v1
data:
  contour.yaml: >
    globalExtAuth:
      extensionService: auth-server/auth-server
      failOpen: false
      responseTimeout: 2s
      ...

And our extension service is configured like this:

spec:
...
  timeoutPolicy:
    response: 2000ms

What did you expect to happen:
I expect a 2 second timeout for authorization requests.

Anything else you would like to add:
not at this time

Environment:

  • Contour version: v1.30.0
  • Kubernetes version: 1.31
  • Kubernetes installer & version: EKS
  • Cloud provider or hardware configuration: AWS
  • OS (e.g. from /etc/os-release): bottlerocket
@kncesarini kncesarini added kind/bug Categorizes issue or PR as related to a bug. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Dec 18, 2024
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant