-
Notifications
You must be signed in to change notification settings - Fork 193
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
Define custom annotations for LB Service #524
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I realize this response is very belated, but this enhancement proposal would add an API for configuring the idle timeout on AWS LBs: openshift/enhancements#461 Unfortunately I cannot say at this time in which version of OpenShift the enhancement will be implemented. There is no general API to tell the operator to set arbitrary annotations on operands. |
Thanks for the information. I don't remember if whether we just updated the idle timeouts manually or created the corresponding Service resource with the annotation to set the idle timeout. Anyhow, it's great that a more proper way of setting the idle timeout is coming. |
Hi,
Is it possible to define own annotations that would get passed to the LB service created by cluster-ingress-operator? Specifically, I'm interested in adding service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout to override the default idle timeout (60s) for AWS Classic LB. I know I could add this directly to the created service but we are using gitops for OpenShift configuration and I would prefer to not to modify resources created by operators but instead modify the Ingress (cluster) or IngressController (default) resources.
We currently have OS v4.5.15 installed.
The text was updated successfully, but these errors were encountered: