Engineering Release Summary for April and May 2019
It’s been a little while since we last posted a release summary and these past couple of months have been busy fixing bugs, adding new features and releasing introducing new products. Also want to thank the following people in the community for their contributions to the releases in April and May: techmunk, johscheuer, chtison, Harwayne, jonsabo, arindam-bandyopadhyay and peterj!
Check out our GitHub repo to file any issues or PRs and join our community to ask questions.
New Service Mesh Hub
Launched at KubeCon EU, Service Mesh Hub is a dashboard built on top of SuperGloo for everything and anything service mesh. You can install or discover any mesh (App Mesh, Istio, Linkerd), deploy and manage the services on them and install 3rd party extensions. Try it out and give us feedback
New Gloo Shot
Launched at KubeCon EU, Gloo Shot is a project to run Chaos Engineering experiments to stress test distributed applications. We have had 4 releases already but are only getting started so try it out and give us feedback.
SuperGloo project is now v0.3.20
Check out the changelog here to see all the fixes and new features. In the last couple of months we have added features to support the SMI spec and discovery and configuration support for Linkerd and AWS App Mesh.
Here are some highlights of SuperGloo new features:
- Add a new smi-install option to the supergloo install istio command to deploy the SMI Istio adapter together with Istio. (https://github.com/solo-io/supergloo/issues/458)
- Enable SMI discovery and translation (https://github.com/solo-io/supergloo/issues/456)
- Add automated linkerd ingress with gloo. (https://github.com/solo-io/supergloo/issues/422)
- Add mesh discovery for AWS app mesh (https://github.com/solo-io/supergloo/issues/407)
- Add config discovery for appmesh, include upstreams in discovery meta (https://github.com/solo-io/supergloo/issues/409)
- Enable Config Translation for Linkerd. Supports Retry Routing Rules (https://github.com/solo-io/supergloo/issues/370)
- Install Linkerd from the CLI. (https://github.com/solo-io/supergloo/issues/350)
- Enable Linkerd Installation (https://github.com/solo-io/supergloo/issues/354)
- Mesh discovery. (https://github.com/solo-io/supergloo/issues/213)
Gloo Gateway Open Source is now v0.13.29
Here is the list of new features and fixes for the Gloo Gateway. View the changelog or submit issues and pull requests here. We made lots of improvements to our API gateway based on your feedback and comments. Also if you want to try our enterprise version, sign up here.
Gloo Gateway New Features:
- Expose gloo and envoy stats by default (https://github.com/solo-io/gloo/pull/710)
- Add upstream group to glooctl add route (https://github.com/solo-io/gloo/pull/709)
- Enable linkerd header addition on gloo upstreams. (https://github.com/solo-io/supergloo/issues/422)
- Don’t write envoy config to disk so we can work with read only root fs. Add a strict SecurityContext to manifests. (https://github.com/solo-io/gloo/pull/693)
- Solves part of https://github.com/solo-io/gloo/issues/668 — allow configuration connection settings. (https://github.com/solo-io/gloo/issues/668)
- Add proxy protocol support for gateway deployments. (https://github.com/solo-io/gloo/pull/676)
- Update knative-serving installation to version 0.5.1 (https://github.com/solo-io/gloo/pull/673)
- Validate key pair during glooctl create secret tls. (https://github.com/solo-io/gloo/issues/546)
- Choose namespace from list in glooctl interactive mode. (https://github.com/solo-io/gloo/issues/552)
- Allow configuring upstream load balancer settings. (https://github.com/solo-io/gloo/issues/652)
- Add shell completion to glooctl. (https://github.com/solo-io/gloo/issues/460)
Gloo Gateway Fixes:
- Only use ipv4 for admin, to avoid failures when ipv6 not present. (https://github.com/solo-io/gloo/pull/716)
- Fix non existent var when using extra annotations for service (https://github.com/solo-io/gloo/issues/714)
- Use underscores instead of dots in the cluster name, for better prometheus stats. (https://github.com/solo-io/gloo/pull/712)
- Quote annotations in helm chart (https://github.com/solo-io/gloo/pull/711)
- Add Tcp keep alive to the static config to assist in detecting half open connections. (https://github.com/solo-io/gloo/pull/708)
- Adds the missing CLlsterRole for knative-build access of the knative-serving controller. (https://github.com/solo-io/gloo/issues/704)
- Fix bug that caused gloo to always watch all namespace regardless of the value set on thr settings CRD. (https://github.com/solo-io/gloo/issues/694)
- Allow gateway-proxy to transparently work in conjunction with linkerd-proxy (https://github.com/solo-io/gloo/issues/691)
- Fix knative test flake (https://github.com/solo-io/gloo/issues/685)
- Allow upstream discovery discovery grpc services correctly. (https://github.com/solo-io/gloo/issues/688)
- Pull in new envoy-gloo with fix for remove content-type on transformation fix. (https://github.com/solo-io/gloo/issues/682)
- Do not require root ca for glooctl create secret tls. (https://github.com/solo-io/gloo/issues/546)
- Use latest envoy to address envoy security release. (https://github.com/solo-io/gloo/pull/665)
- Include subresource status in glooctl get virtualservice output. (https://github.com/solo-io/gloo/issues/297)
Squash is now v0.5.15
Our microservices debugger has been featured in some recent talks at both DockerCon and KubeCon EU and we can’t wait for you to try it and send in requests and feedback. View the entire changelog here and check out the highlights below.
Squash New Features:
- Allow using a custom kubeconfig (https://github.com/solo-io/squash/issues/182)
- Added support for auth plugins in kube config (https://github.com/solo-io/squash/issues/168)
- Add optional verbose flag to vscode extension for self-diagnostics. (https://github.com/solo-io/squash/issues/141)
- Allow flags to override default Squash image. (https://github.com/solo-io/squash/issues/132)
Squash Fixes
- Fix squashctl utils delete-planks to only delete plank pods, rather than all pods in squash namespace. (https://github.com/solo-io/squash/issues/162)
- squashctl’s –container flag is now the container’s name, not image. (https://github.com/solo-io/squash/issues/159)
- Choose the container to debug via the VS Code extension. (https://github.com/solo-io/squash/issues/160)
- Include process arguments in output from java port not found error. (https://github.com/solo-io/squash/issues/156)
- Add documentation on how to build squash from source. (https://github.com/solo-io/squash/issues/149)
- Fix Role Binding for Custom Namespace. (https://github.com/solo-io/squash/issues/147)
- Consolidated code to get Kubernetes Context client, and added better error handling. (https://github.com/solo-io/squash/issues/154)
- Fix download url for squashctl. (https://github.com/solo-io/squash/issues/145)
- When deploying demos, just print app type, not deployment details. (https://github.com/solo-io/squash/issues/125)
- Clean up test resources to improve CI stability. (https://github.com/solo-io/squash/issues/140)
- Fix name of Squash image. (https://github.com/solo-io/squash/issues/136)
- Use new container repo (quay) for Squash image. (https://github.com/solo-io/squash/issues/130)
About the Author
