v1.2.7

Fixes

• Return an error from the validation server if ValidateProxy is called before the first Sync has happened (solo-io#1873)

v1.2.6

New Features

• Experimental support for envoy-wasm (solo-io#1868)

v1.2.5

Dependency Bumps

• envoy-gloo/solo-io has been upgraded to v0.1.19. This includes the security fixes introduced in upstream envoy 1.12.2.

Fixes

• AWS function discovery is more painful after our change to make FDS run in Whitelist mode by default. This changes FDS so that, in Whitelist mode, AWS functions are discovered as if FDS is running in Blacklist mode. (solo-io#1878)
• By default, glooctl install will now attempt to create the namespace to install gloo into. This is a prerequisite for actually installing gloo, but can be turned off with the install flag --create-namespace=false. (solo-io#1871)
• Previously, virtual service validation treated a virtual host with a domain of "" (empty string) as having a domain of "*". This then had the potential to conflict with virtual services that legitimately have a domain of "*". Now we report an error from virtual service validation when a domain is the empty string. (solo-io#1885)
• Output the glooctl version warning to stderr rather than stdout. Also, base the decision on whether or not to warn about a version mismatch solely on the versions of the open-source discovery containers that we find in the cluster. (solo-io#1852)
• Use klog shim so that klog doesn't attempt to write files. (solo-io#1039)

v1.2.4

Fixes

• Readd version.EnterpriseTag for test overrides and future flag overrides. (solo-io#1861)

v1.2.3

Fixes

• Calculate the enterprise tag from the gloo-ee helm repo index file (https://storage.googleapis.com/gloo-ee-helm/index.yaml) instead of hardcoding it. (solo-io#1831)
• Ensure that our usage of the Helm client libraries assigns a namespace to all resources, even those whose YAML definition does not specify a namespace. This is to fix the bug where observability resources can wind up in the default namespace set by the user's kube config; as of the time of writing, Prometheus's chart defines resources that are namespaced but do not have a namespace explicitly set on them. (solo-io#1857)
• The recent v1.2.0 release updated the Gloo chart to be compatible with Helm 3. This included moving the CRDs to the new dedicated /crd directory inside the chart. Helm 2 is not aware of this directory and hence will never render the CRDs. This fix adds back a CRD template file in the templates directory to make the chart backwards-compatible with Helm 2. (solo-io#1835)
• We currently allow setting the ttlSecondsAfterFinished attribute on the certgen job via the gateway.certGenJob.ttlSecondsAfterFinished Helm value. Since this attribute was introduced with kubernetes 1.12, we here introduce a check in the Helm template to not render it if the version of kubernetes is less than 1.12. (solo-io#1853)

v1.2.2

This release was canceled.

Fixes

• Quick fix for regression on FDS with non-kube upstreams. (solo-io#1844)

v1.2.1

Fixes

• The template for the settings resource needs to be a Helm pre-install hook to prevent races during install. The hook annotation was accidentally removed with the 1.2.0 release; this change adds it back. (solo-io#1838)

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. (solo-io#1775)
• Added hook-delete-policy to clean up the validation webhook certificate generation job after it has successfully completed. (solo-io#1732)

New Features

• Gloo Validation now always rejects resources which fail to unmarshal, even when strict validation is disabled. (solo-io#1795)
• The Gloo Helm chart is now compatible with Helm 3. (solo-io#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 (solo-io#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). (solo-io#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. (solo-io#1732)
• Add advanced rule priority options to Gloo Enterprise rate limit API, which will be supported in the next 1.x Gloo Enterprise release. (solo-io#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. (solo-io#1695)

Fixes

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

v1.1.0

Helm Changes

• Add the Helm field extraEnvoyArgs to .Values.gatewayProxies.gatewayProxy so users can add additional envoy command line arguments (e.g. --component-log-level "upstream:trace,misc:error", to set log levels for individual envoy components). See the full list of Envoy command line args here - https://www.envoyproxy.io/docs/envoy/latest/operations/cli (solo-io#1737)

New Features

• Bump default version of Knative Serving installed via glooctl install to 0.10.0 (solo-io#1761)
• Add the Helm field .Values.gatewayProxies.gatewayProxy.extraEnvoyArgs so users can add additional envoy command line arguments (e.g. --set component-log-level="...", to set log levels for individual envoy components). See the full list of Envoy command line args here - https://www.envoyproxy.io/docs/envoy/latest/operations/cli (solo-io#1737)
• Allow multiple value files to be passed in during installation, (e.g. glooctl install gateway --dry-run --values file1.yaml,file2.yaml --values file3.yaml). (solo-io#1731)

v0.21.3

New Features

• The default version of GlooE installed by the CLI is now 0.21.0. (solo-io#1725)