Orchestrating Dead-Simple Service Meshes With Supergloo

Currently, the most well-known service mesh is Istio with the backing of Lyft, Google, and IBM. However, there are many options to choose from. Service meshes are all the rage in the Kubernetes world these days, but a lot of people seem to be a bit confused as to what they do and why (when) they need one. The best way to think of a service mesh is to imagine well...a mesh!

What Is a Service Mesh?

Service meshes are all the rage in the Kubernetes world these days, but a lot of people seem to be a bit confused as to what they do and why (when) they need one. The best way to think of a service mesh is to imagine well...a mesh! The service mesh is a configurable, low‑latency infrastructure layer designed to handle communication between the processes among different services using application programming interfaces (APIs). It ensures that communication among containerized and often ephemeral application infrastructure services is fast, reliable, and secure. The mesh also provides critical capabilities that include:

• Service discovery
• Load Balancing
• Encryption
• Observability
• Authentication

The service mesh is usually implemented by providing a proxy instance, called a sidecar, for each service instance. Sidecars handle inter-service communications, monitoring, and security‑related concerns - anything can be abstracted away from the individual sources. This way, developers can handle development, support, and maintenance for the application code in the services; operations teams can maintain the service mesh and run the app.

Currently, the most well-known service mesh is Istio with the backing of Lyft, Google, and IBM. However, there are many options and the tool I'm going to show you today is going to help you get started with your first service mesh on various platforms.

Let's go ahead and check out SuperGloo!

What Is SuperGloo?

With all of the varied offerings in the service mesh landscape, it makes it difficult to take on the complexities of experimenting with even a single service mesh solution, let alone multiple ones. The goal of SuperGloo is to take charge of these complexities and make it easy for users to deploy multiple service meshes into their environment.

SuperGloo abstracts away key functionalities associated with the service mesh such as:

• Encryption
• Telemetry
• Tracing

Using tools like SuperGloo, you can pair any service mesh with any ingress, and leave it to the abstraction to take care of the installation and configuration necessary to let them work together.

Let's try it out!

Getting Started With SuperGloo

Prerequisites

• A running Kubernetes cluster
• Helm (Optional)

Installing a Command-Line Tool (CLI)

The supergloo command-line makes it much easier to install and operate SuperGloo, though it is not required.

To install using the Homebrew package manager, run the following.

brew install solo-io/tap/supergloo

To install on any platform run the following.

curl -sL https://run.solo.io/supergloo/install | sh

You can download the CLI directly via the GitHub releases page. You need to add SuperGloo to your path after downloading.

export PATH=$HOME/.supergloo/bin:$PATH

Verify the CLI is installed and running correctly with:

supergloo --version

cloud kubernetes microservice cloud native service mesh

Our original Kubernetes tool list was so popular that we've curated another great list of tools to help you improve your functionality with the platform.

Article covers: How native is react native?, React Native vs (Ionic, Cordova), Similarities and difference between React Native and Native App Development.

Mismanagement of multi-cloud expense costs an arm and leg to business and its management has become a major pain point. Here we break down some crucial tips to take some of the management challenges off your plate and help you optimize your cloud spend.

In this article, take a look at the service mesh in the microservices world. The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.

Aspen Mesh's Andrew Jenkins and Tetrate's Zack Butcher cover how service mesh and Istio help teams get more out of containers and Kubernetes.