Gloo Edge 1.14 is here!
Today we are excited to introduce the latest version of Gloo Edge! With Gloo Edge 1.14 we continue to improve on the features our customers rely on every day. From updating the integrations that are part of your operations, to improving features that are enhancing the way you operate, there are many reasons to continue your Gloo Edge journey with our latest release.
AWS Lambda integration enhancements
With more of our customers relying on the serverless capabilities of AWS Lambda, we have spent time improving the integration between Gloo Edge and Lambda to bring containerized services and serverless functions more closely together. Multiple improvements have been done in areas such as response or request transformation as well as when delegating Lambda instances.
Connecting through gRPC
As a high-performance open source method to support millions of RPCs per second, gRPC support is becoming required for some of our high volume customers. Our gRPC Implementation received some frequently asked upgrades, especially in the area of transcoding from traditional HTTP APIs to grpc. Since gRPC requires proto definition, Gloo Edge needs to be aware of them. Now, automatic discovery of those descriptors is supported for mappings. This is great, because it helps configuring Gloo Edge to accept incoming HTTP requests and translate these requests to gRPC requests so that they can be processed by the gRPC upstream.
Portal and GraphQL updates your developers will love
Platform engineers can help their developers be more successful by introducing them to the Portal and GraphQL capabilities available in Gloo Edge.
Gloo Portal is used heavily by many customers and their respective development teams. As a result, multiple different personas are utilizing the portal to manage the APIs published. Gloo Portal 1.3 adds an admin UIwith RBAC via Kubernetes roles. Also, it’s now possible to configure a general rate limit for a given API which applies to the entire consumer base and is not specified to one single consumer. Once APIs are published, you will get to the point quickly to try out those APIs through the rendered OpenAPI specification in the portal. JWT has been added here as an auth option.
The biggest enhancement GraphQL received is the possibility to discover remote executors automatically. That is a pre-requirement to auto generate the needed Kubernetes resources. This saves the user the trouble of creating a CR on their own with the schema and upstream API details and enhancing their productivity.
Kubernetes 1.25 support
Kubernetes 1.25 proved to be a major change around the way security was managed. Supporting the 1.25 release led to extra engineering efforts to ensure none of the security API changes would interfere with operations. The engineering team at Solo has combed through all the changes and has built support for Kubernetes 1.25 into Gloo Edge 1.14.
Stability, Stability, Stability
With every release, our engineers spend a number of cycles making sure Gloo Edge can exceed the reliability requirements of our customers. That means stability is a key factor for any Gloo Edge release. With Gloo Edge 1.14, we continue to deliver stability enhancements that matter to our customers.
What’s coming up for Gloo Edge?
There are additional enhancements coming to Gloo Edge 1.15 targeted for release in July 2023. In addition to adding functionality asked for by our customer base, we are looking forward to providing official ARM Images to allow Gloo Edge to run in environments like AWS Gravitron. Also, OCSP stapling and the automation of fetching is a topic we want to work on. Last but not least, we are also investigating TAPing into the network stream, to help our customers who need to live tap into network streams and potentially forward them to a third party system for thread detection.
