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

responseTimeout not applied for external auth extension service #6536

Open
clayton-gonsalves opened this issue Jul 1, 2024 · 2 comments
Open
Assignees
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

@clayton-gonsalves
Copy link
Contributor

When defining the responseTimeout for ext auth extension service. the timeout is not applied.

What did you expect to happen:
Timeout supplied of the ext auth config should be applied.

Environment:

  • Contour version: Latest
  • Kubernetes version: 1.28
@clayton-gonsalves clayton-gonsalves 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 Jul 1, 2024
@clayton-gonsalves clayton-gonsalves self-assigned this Jul 1, 2024
@clayton-gonsalves
Copy link
Contributor Author

@skriss @sunjayBhatia @tsaarni
Since this field isn't working and i am not sure if it ever did, what do you folks think about deprecating it on the global config with a message(we still keep it for backward compatibility).

And only use the the extension service crd to control the timeouts?

Copy link

github-actions bot commented Sep 2, 2024

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 Sep 2, 2024
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