gloo

Fixes

• EC2 upstream should default to port 80. (https://github.com/solo-io/gloo/issues/873)
• glooctl should display EC2 type name. (https://github.com/solo-io/gloo/issues/874)

New Features

• EC2 upstreams do not need to provide an AWS secret, it can be taken from the environment. (https://github.com/solo-io/gloo/issues/864)

Fixes

• Improve glooctl error message for malformed upstreams (https://github.com/solo-io/gloo/issues/655)
• gRPC plugin to handle missing path matcher (https://github.com/solo-io/gloo/issues/860)

New Features

• Translate Consul routing destinations. (https://github.com/solo-io/gloo/issues/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. (https://github.com/solo-io/gloo/issues/828)
• Use map structure in values-gateway-template yaml so gateway proxy values can be easily overridden. (https://github.com/solo-io/gloo/issues/857)
• Make sure translator errors on routes without a path match (https://github.com/solo-io/gloo/issues/860)

New Features

• Add the ability to deploy the gateway-proxy as a DaemonSet rather than a deployment. (https://github.com/solo-io/gloo/issues/842)

This release contained no user-facing changes.

New Features

• Added Consul endpoint discovery. (https://github.com/solo-io/gloo/issues/803)
• Introduce EC2 upstream type. (https://github.com/solo-io/gloo/issues/799)

Fixes

• Fix Endpoints getting lost in Kubernetes EDS. (https://github.com/solo-io/gloo/issues/816)
• Fix a bug with handling of gRPC upstreams without a package (https://github.com/solo-io/gloo/issues/831)

Breaking Changes

• Rename existing service destination type from service to kubernetes. (https://github.com/solo-io/gloo/issues/803)

New Features

• Add new routing destination type for Consul services. (https://github.com/solo-io/gloo/issues/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. (https://github.com/solo-io/gloo/issues/679)
• Knative installation via the CLI is now version-independent, allows installing additional Knative components Build, Eventing, and Monitoring (https://github.com/solo-io/gloo/issues/795)

Fixes

• Fix an issue where routing to a grpc upstream using parameters did not work. (https://github.com/solo-io/gloo/issues/809)

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 (https://github.com/solo-io/gloo/issues/801)

This release build failed.

Dependency Bumps

• solo-io/go-utils has been upgraded to v0.8.23.
• solo-io/solo-kit has been upgraded to v0.9.13.
• solo-io/solo-kit has been upgraded to v0.10.0.

Breaking Changes

• Expose use_http2 field on upstream spec. The use_http2 field has been removed from the Static UpstreamSpec (https://github.com/solo-io/gloo/issues/787)
• Introduce vhost params for gloo plugins (https://github.com/solo-io/gloo/pull/796)

New Features

• allow disabling fds on a per-namespace and per-service basis (https://github.com/solo-io/gloo/issues/679)

Fixes

• When the translation of the Gloo API snapshot to the xDS one returns an error we currently skip updating the xDS cache. Gloo attempts to remove errored upstreams without compromising the consistency of the snapshot, but most errors still result in the xDS cache not being updated. By not updating the cache, Envoy will continue using the previous snapshot, which we assume to be valid. The problem with this approach is that endpoints are relatively ephemeral entities (think Kubernetes pods) and the snapshot that Gloo is using might become stale if any endpoint changes. With this fix Gloo will try to update the EDS information in the xDS cache even if an error occurred during translation. It does so by retrieving the previous xDS snapshot, updating only the EDS information, verifying the consistency of the resulting snapshot, and, if consistent, persisting it in the cache. (https://github.com/solo-io/gloo/issues/657)
• Fix race condition where helm chart sometimes wouldn't publish on release builds. (https://github.com/solo-io/gloo/issues/785)
• support Knative Version 0.7.0 by setting ClusterIngress.Status (https://github.com/solo-io/gloo/issues/779)
• fix missing hosts on clusteringress proxy translation (https://github.com/solo-io/gloo/issues/790)
• provide rbac for updating clusteringress/status (https://github.com/solo-io/gloo/issues/789)
• enable http2 for ports with prefix http2 (https://github.com/solo-io/gloo/issues/788)

Fixes

• An error in the main syncer no longer prevents syncer extensions from running. Similarly, a bad extension syncer will no longer block other extension syncers from running. (https://github.com/solo-io/gloo/issues/783)

New Features

• provide option for the helm chart to install gloo knative integration without installing knative itself (https://github.com/solo-io/gloo/issues/774)

Fixes

• Use apps/v1 api group for deployments (https://github.com/solo-io/gloo/issues/767)
• fix append in hybridUpstreamSnapshot (https://github.com/solo-io/gloo/issues/771)

Breaking Changes

• Bumping minor version after the breaking API change from release 0.13.34 (which erroneously did not bump it). (https://github.com/solo-io/gloo/issues/760)
• Fixing misspelled ssl_configuations field in Listener protobuf message. (https://github.com/solo-io/gloo/issues/762)
• Extend the route params for the plugins to have the vhost included. (https://github.com/solo-io/gloo/pull/766)

New Features

• Updated Route API to allow Kubernetes services as direct routing destinations. This means that, in addition to
  Upstreams, Routes on VirtualService and Proxy resources can now directly point to a Kubernetes service. (https://github.com/solo-io/gloo/issues/746)
• Add Virtual Clusters to the Gloo API. (https://github.com/solo-io/gloo/issues/764)

New Features

• Update API to support routing to Kubernetes services. (https://github.com/solo-io/gloo/issues/746)

Fixes

• Fix hardcoded Kubernetes cluster name in a Helm Chart (https://github.com/solo-io/gloo/issues/754)

This release contained no user-facing changes.

New Features

• Allow two virtual services on the same host with identical SslConfigs to be merged (https://github.com/solo-io/gloo/issues/731)

This release build failed.

New Features

• Update transformation config to allow for clearing the route cache. (https://github.com/solo-io/gloo/pull/740)

Fixes

• Fix interactive CLI command to add routes to Virtual Services. (https://github.com/solo-io/gloo/pull/737)

New Features

• Allow disabling function discovery. This can now be done with --set discovery.disable_fds=true when installing with helm. (https://github.com/solo-io/gloo/pull/729)

Fixes

• Allow two virtual services on the same host, differing by ssl/non-ssl (https://github.com/solo-io/gloo/pull/734)
• Add tcp keepalive to knative and ingress projects. (https://github.com/solo-io/gloo/pull/728)

Fixes

• Only use ipv4 for admin, to avoid failures when ipv6 not present. (https://github.com/solo-io/gloo/pull/716)

Fixes

• Fix non existent var when using extra annotations for service (https://github.com/solo-io/gloo/issues/714)