v1.13.0-rc1

New Features

• Allow regression tests to be run against released versions of gloo in addition to local builds. (solo-io/solo-projects#4191)

v1.12.35

Fixes

• Fix for issue where multiple routes defined for the same upstream would remove the UpstreamTlsContext associated with the tunneling cluster and all requests would be sent through the tunnel as http. (#7313)

v1.10.41

Fixes

• Fix for issue where multiple routes defined for the same upstream would remove the UpstreamTlsContext associated with the tunneling cluster and all requests would be sent through the tunnel as http. (#7313)

v1.9.30

Fixes

• Fix for issue where multiple routes defined for the same upstream would remove the UpstreamTlsContext associated with the tunneling cluster and all requests would be sent through the tunnel as http. (#7313)

v1.2.0

Dependency Bumps

• envoyproxy/go-control-plane has been upgraded to v0.9.0.
• knative/serving has been upgraded to v0.10.0.
• solo-io/go-utils has been upgraded to v0.11.0.
• solo-io/reporting-client has been upgraded to v0.1.2.
• k8s.io/api has been upgraded to kubernetes-1.16.2.
• k8s.io/client-go has been upgraded to kubernetes-1.16.2.
• k8s.io/kubectl has been upgraded to kubernetes-1.16.2.
• k8s.io/apimachinery has been upgraded to kubernetes-1.16.2.
• k8s.io/apiextensions-apiserver has been upgraded to kubernetes-1.16.2.
• k8s.io/apiserver has been upgraded to kubernetes-1.16.2.

Helm Changes

• Move gatewayProxies.NAME.kind.deployment.antiAffinity Helm value out into gatewayProxies.NAME.antiAffinity, since it can be applied to both DaemonSets and Deployments. (#1775)
• Added hook-delete-policy to clean up the validation webhook certificate generation job after it has successfully completed. (#1732)

New Features

• Gloo Validation now always rejects resources which fail to unmarshal, even when strict validation is disabled. (#1795)
• The Gloo Helm chart is now compatible with Helm 3. (#1732)
• Refactor glooctl to make it compatible with the new Helm 3 chart format. glooctl now uses the new Helm 3 libraries and delegates the install and uninstall operations to the corresponding Helm functions to provide consistent behavior across different installation flows; for example, it is now possible to install Gloo using glooctl and uninstall it using Helm, or vice-versa (#1732)
• Deprecated the installConfig.installationId Helm value to track the resources that belong to a Gloo installation. Helm keeps track of resources by storing release information in a Kubernetes Secret in the namespace Gloo was installed in (this is the default with Helm 3 and can be changed via the HELM_DRIVER environment variable). glooctl install and glooctl uninstall now take the same approach (under the hood the two commands now delegate to their counterparts in the Helm 3 libraries). (#1635)
• Helm users can now easily install Gloo in ingress or knative mode by using value overrides. The Gloo Helm chart now packages a single values file instead of creating variants for ingress and knative. The values specific to those two installation modes have been merged into the default values.yaml, where they will be ignored when those two features are disabled (which is the default). To produce the manifests specific to the ingress and knative installations, users can now just disable the gateway and enable the desired component via Helm value overrides. (#1732)
• Add advanced rule priority options to Gloo Enterprise rate limit API, which will be supported in the next 1.x Gloo Enterprise release. (#1724)
• Add virtual_service_namespaces configuration to the HttpGateway, which allows HttpGateways to reference VirtualServices outside of their own namespace using the label selector. The default behavior, which remains unchanged, is to restrict gateways to referencing virtual services in their own namespace. (#1695)

Fixes

• Fix a crash in Gloo that occurs when no kubeconfig is present
  (which is expected in non-Kubernetes environments). (#1777)