v0.1.16-hotfix2

This is a hotfix release based on v0.1.16-hotfix1. It fixes a regression related to sticky sessions.

We set the protocol to HTTP if the sticky sessions option was set. However, this prevents concurrent usage of TCP and sticky HTTPS.

The release reverts the logic to the previous state.

Check out the CHANGELOG for more details.

v0.1.16-hotfix1

This is a hotfix release based on v0.1.16. It fixes a regression related to health check path handling.

Prior to that release, the service protocol would also be used as the default health check protocol. v0.1.16 changed the behavior to default to TCP which breaks scenarios where a health check path is defined only. Without an accompanying health check protocol set to HTTP explicitly, the LB API would reject such requests accordingly.

The hotfix provides a patch that defaults the health check protocol to HTTP if a health check path is specified.

Check out the CHANGELOG for more details.

v0.1.16

This release includes:

• support for HTTP/2
• more reasonable default values when specific load-balancer annotations are set
• small bug fixes around load-balancer deletions

Check out the CHANGELOG for more details.

v0.1.15

Notable changes:

• Node bootstrapping should be more performant in terms of latency
• The flags allow-untagged-cloud and cloud-provider do not need to be set explicitly anymore. They are now set implicitly in-code.
• The user agent when talking to the DigitalOcean API is set to digitalocean-cloud-controller-manager/<CCM version>
• The flag authentication-skip-lookup=true is set implicitly (fixes #217)

Check out the CHANGELOG for more details.

v0.1.14

Check out the CHANGELOG for more details.

v0.1.13

Check out the CHANGELOG for more details.

v0.1.12

Check out the CHANGELOG for more details.

v0.1.11

Check out the CHANGELOG for more details.

v0.1.10

Check out the CHANGELOG for more details.

v0.1.9

IMPORTANT: This release contains a significant bug. Use v0.1.10 instead.

Check out the CHANGELOG for more details.