v0.18.1

In Gloo 0.18.1, we added support for TCP proxying, which required a breaking change to the gateway API.
Please check out https://gloo.solo.io/upgrading/0.18.1/ for details on how to seamlessly upgrade Gloo,
automatically convert existing configuration, and migrate traffic while avoiding downtime.

New Features

• Add access logging capability to gloo. (#814)
• Add glooctl support for creating and deleting upstream groups (#649)
• Allow setting resource limits in the helm chart. (#889)

v0.18.0

This is a pre-release. Please don't deploy this, instead use 0.18.1.

In Gloo 0.18.1, we added support for TCP proxying, which required a breaking change to the gateway API.
Please check out https://gloo.solo.io/upgrading/0.18.1/ for details on how to seamlessly upgrade Gloo,
automatically convert existing configuration, and migrate traffic while avoiding downtime.

Breaking Changes

• update the gateway API in preparation for TCP proxy (#778)
• update the gateway to have multiple types to support tcp proxy (#778)
• Settings CRD has been refactored to reflect Consul changes. (#883)

New Features

• add ability to print basic non-kube yaml with cli commands (#896)
• Add liveness and readiness probes (#872)
• Fix race condition where helm chart sometimes wouldn't publish on release builds. (#778)
• Add support for tolerations to gateway-proxy (#877)
• Enable tracing. (#879)
• Enable running Gloo using Vault as a Secret backend and Consul as a configuration Backend. (#883)

Fixes

• glooctl interactive prompts display updated state (#551)
• Make liveness work even when there is no gloo config. (#872)
• Fix an unlikely edge case where a client might emit an incomplete list of upstreams. (#886)
• fix issue with partial EDS where clusters were out of sync with endpoints (#899)

v0.17.6

Fixes

• EC2 upstream should default to port 80. (#873)
• glooctl should display EC2 type name. (#874)

v0.17.5

New Features

• EC2 upstreams do not need to provide an AWS secret, it can be taken from the environment. (#864)

Fixes

• Improve glooctl error message for malformed upstreams (#655)
• gRPC plugin to handle missing path matcher (#860)

v0.17.4

New Features

• Translate Consul routing destinations. (#803)

Fixes

• Bump solo-kit to a version where CRDs are registered with both Version and Versions set.
  This fixes gloo installation on Kubernetes 1.10 when CRDs are not created via helm chart. (#828)
• Use map structure in values-gateway-template yaml so gateway proxy values can be easily overridden. (#857)
• Make sure translator errors on routes without a path match (#860)

v0.17.3

New Features

• Add the ability to deploy the gateway-proxy as a DaemonSet rather than a deployment. (#842)

v0.17.2

This release contained no user-facing changes.

v0.17.1

New Features

• Added Consul endpoint discovery. (#803)
• Introduce EC2 upstream type. (#799)

Fixes

• Fix Endpoints getting lost in Kubernetes EDS. (#816)
• Fix a bug with handling of gRPC upstreams without a package (#831)

v0.17.0

Breaking Changes

• Rename existing service destination type from service to kubernetes. (#803)

New Features

• Add new routing destination type for Consul services. (#803)
• Allow disabling FDS on a per-namespace and per-service basis with blacklist/whitelist options.
  Note that kube-system and kube-public namespaces must be explicitly whitelisted even in
  blacklist mode. (#679)
• Knative installation via the CLI is now version-independent, allows installing additional Knative components Build, Eventing, and Monitoring (#795)

Fixes

• Fix an issue where routing to a grpc upstream using parameters did not work. (#809)

v0.16.0

Dependency Bumps

• solo-io/solo-kit has been upgraded to v0.10.2.
• solo-io/go-utils has been upgraded to v0.9.1.

Breaking Changes

• Change how listener plugins are arranged on the proxy object (#801)