v0.14.0

Features:

• Profiling library is added by default: this will allow profiling using the metrics endpoint to get profiling data in case of memory leaks, too much CPU cycles, etc

• Add ability to disable backend keep alives: until now, keep alive signals were always enabled. This can reduce latency at the cost of consuming more memory. This flag helps on those scenarios where consuming CPU is preferred over memory consumption.

  Related option:

  • http_backend_disable_keep_alives

Contributors:
@achetronic

hashrouter-helm-chart-0.14.0

A Helm chart for hashrouter, a zero-dependencies HTTP proxy that truly routes requests hash-consistently

v0.13.0

Features:

• Add ability to disable server keep alives: until now, keep alive signals were always enabled. This can reduce latency at the cost of consuming more memory. This flag helps on those scenarios where consuming CPU is preferred over memory consumption.

  Related option:

  • http_server_disable_keep_alives

Contributors:
@achetronic

hashrouter-helm-chart-0.13.0

A Helm chart for hashrouter, a zero-dependencies HTTP proxy that truly routes requests hash-consistently

v0.12.0

Features:

• Add ability to configure several client/server timouts: until now, the only configurable timeout was the maximum time in milliseconds to wait for the entire backend request to complete, including both connection and data transfer.

  Now, there are params to configure other timeouts related to the server and the client such as:

  • http_server_read_timeout_ms
  • http_server_write_timeout_ms
  • http_backend_dial_timeout_ms
  • http_backend_keep_alive_ms

Contributors:
@achetronic

hashrouter-helm-chart-0.12.0

A Helm chart for hashrouter, a zero-dependencies HTTP proxy that truly routes requests hash-consistently

v0.11.1

Fixes:

• Implement case insensitive-ness in ${REQUEST_HEADER:<example>} tags: until now, some replacements were not working due to a pre-capitalization of the tag before looking for the value inside the request. This is not happening anymore, so tags are case-insensitive

Contributors:
@achetronic

v0.11.0

Changes:

• Now, replacement tags (those with pattern ${REPLACEMENT}) doesn't produce errors when missing: they produce empty strings as this is a much more predictable behavior for users

• ${REQUEST_HEADER:<example>} tags can be used as part of hash key pattern on configuration

Contributors:
@achetronic

hashrouter-helm-chart-0.11.1

A Helm chart for hashrouter, a A zero-dependencies HTTP proxy that truly routes requests hash-consistently

hashrouter-helm-chart-0.11.0

A Helm chart for hashrouter, a A zero-dependencies HTTP proxy that truly routes requests hash-consistently