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
Add support for adjusting ELB idle timeout for apiserver #1886
Add support for adjusting ELB idle timeout for apiserver #1886
Conversation
Hi @zacblazic. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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 understand the commands that are listed here. |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.
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 understand the commands that are listed here. |
I signed it! |
@zacblazic can we rebase this? Flannel integration test will throw an error on merging this into master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please run make apimachinery
to generate the files.
@justinsb additions to the API, could I get a review :) |
Defaults to 5 minutes, but can be adjusted by editing the cluster spec and performing a cluster update.
5eecfb6
to
ce643d0
Compare
I was about to open an issue for this 👍 |
docs/cluster_spec.md
Outdated
@@ -24,11 +24,15 @@ spec: | |||
When configuring a LoadBalancer, you can also choose to have a public ELB or an internal (VPC only) ELB. The `type` | |||
field should be `Public` or `Internal`. | |||
|
|||
Additionally, you can increase idle timeout of the load balancer by setting its `idleTimeoutSeconds`. The default idle timeout is 5 minutes, with a maximum of 1200 seconds (20 minutes) being allowed by AWS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The AWS maximum is 3600. http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in 7eee6f2
LGTM |
@k8s-bot ok to test |
/lgtm Waiting on e2e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - nice fix!
@@ -260,7 +260,8 @@ const ( | |||
) | |||
|
|||
type LoadBalancerAccessSpec struct { | |||
Type LoadBalancerType `json:"type,omitempty"` | |||
Type LoadBalancerType `json:"type,omitempty"` | |||
IdleTimeoutSeconds *int64 `json:"idleTimeoutSeconds,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
int64
might be overkill here, but we can plan for the (very distant) future ;-)
Addresses #1883 by adding an
idleTimeoutSeconds
to theapi.loadBalancer
in the cluster spec:The default timeout value is 5 minutes, and can be adjusted by editing the cluster spec.
P.S. First time contributor, let me know if I've missed something.
This change is