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

release: 0.13.0 #3318

Closed
wants to merge 12 commits into from
Closed

release: 0.13.0 #3318

wants to merge 12 commits into from

Conversation

thibaultcha
Copy link
Member

@thibaultcha thibaultcha commented Mar 20, 2018

Do not merge

TODO:

  • Pull lua-resty-healthcheck version bump
  • Changelog
  • Upgrade path
  • Meta bumps

A few hotfixes cherry-picked from master since 0.13.0rc2: 0.13.0rc2...release/0.13.0

Rebase on top of next before merging into next.

bungle and others added 2 commits March 19, 2018 16:32
Check for the upper bound of all `timeout` and `interval`
fields in the health check configuration.
@thibaultcha
Copy link
Member Author

@hishamhm It seems like a16537c forgot to update the spec-old-api version of the test

@hishamhm
Copy link
Contributor

It seems like a16537c forgot to update the spec-old-api version of the test

@thibaultcha fixed!

hishamhm and others added 3 commits March 20, 2018 14:11
In the upstream event handler, `create_balancer` was being called
with the object received via the event, which contains "id" and
"name" only, and not the entire entity table containing the rest
of the upstream fields. This caused it create a healthchecker with
an empty configuration (ignoring the user's configuration),
which then fell back into the lua-resty-healthcheck defaults.

This fix obtains the proper entity object from the id and passes
it to `create_balancer`.

A regression test is included, which spawns two Kong instances
and reproduces the error scenario described by @mengskysama.

Fixes #3304 
From #3319
The original size was way to low to guarantee proper random
distribution beyond  3-4 targets. The recommended size is 100
slots per target. The new default covers up to 100 targets.

The approximate footprint per Upstream:
- 65535 slots, 100 targets: 1.6MB
- 10000 slots, 100 targets: 375kB

This fix should have been included in the latest update of the
DNS library dependency.

Related #3220 
From #3296
@thibaultcha thibaultcha force-pushed the release/0.13.0 branch 2 times, most recently from dabb325 to 83d0a69 Compare March 21, 2018 01:45
@thibaultcha
Copy link
Member Author

For now, waiting on #3324 for the CI to pass on this branch.

Removes tests that are identical to the ones in spec/

From #3281
@thibaultcha thibaultcha deleted the release/0.13.0 branch March 22, 2018 22:06
@hishamhm
Copy link
Contributor

🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants