Update to haproxy 2.0.11 #414
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
FYI: Upstream haproxy v2.0.8 has been released meanwhile. |
|
.. aaand haproxy v2.0.9 released now aswell. :) |
|
Yup, we're almost there! |
jcmoraisjr
force-pushed
the
jm-haproxy-2.0.7
branch
from
11cd00f to
ba28332
Compare
jcmoraisjr
force-pushed
the
jm-haproxy-2.0.7
branch
from
ba28332 to
8b1788d
Compare
Update also the configuration template in order to remove config parsing warnings
Since haproxy v2.0-dev3 http-use-htx is enabled by default. Changing template and use-htx default configmap option accordingly.
jcmoraisjr
force-pushed
the
jm-haproxy-2.0.7
branch
from
8b1788d to
c912942
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update also the configuration template in order to remove config parsing warnings