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.

Sign up for GitHub

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

Jump to bottom

Allow custom server_names_hash_max_size & server_names_hash_bucket_size #607

Merged
merged 1 commit into from
Apr 15, 2017
Merged

Allow custom server_names_hash_max_size & server_names_hash_bucket_size #607

merged 1 commit into from
Apr 15, 2017

Conversation

aledbf
Copy link
Member

@aledbf aledbf commented Apr 15, 2017 •
edited
Loading

fixes #564

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 15, 2017
@k8s-reviewable
Copy link

This change is Reviewable

@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 46.309% when pulling 9994365 on aledbf:master into c729cd8 on kubernetes:master.

@aledbf aledbf merged commit cd6a212 into kubernetes:master Apr 15, 2017
@aledbf aledbf mentioned this pull request Apr 19, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Wrong calculation for ServerNameHashMaxSize?
4 participants
@aledbf @k8s-reviewable @coveralls @k8s-ci-robot