Skip to content
The Service Mesh Orchestration Platform
Branch: master
Clone or download
EItanya and soloio-bulldozer Gloo mtls cli (#289)
* update on mtls config
* changelog
* ui works for selecting a mesh
* fixed surveyutils test
* dep
* survey test really works
* was creating mesh ingress with wrong namespace
* fixed naming issues with gateway-volumes
* fixed gloo_syncer tests
* post-release changelog move
* dep
* merge commit
* auto-mtls works :)
* new us edit, plus some tests
* cli to edit us works
* code-gen
* finished basic cli functionality
* merge commit
* actually testing gloo installs
* works e2e
* more code-gen
* Merge branch 'master' into gloo-mtls-cli
* switched from edit to set
* code gen for new set cmd
* renamed command to mtls from tls
* merge commit code gen
* removed some logging
* PR comments
* cli change code-gen
* switched zone
Latest commit 72db1ee Mar 26, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
ci checking correct versions of gloo and solo-kit (#262) Mar 15, 2019
docs Gloo mtls cli (#289) Mar 26, 2019
hack clean up after refactor (#246) Mar 14, 2019
mock/pkg rename package (#168) Mar 1, 2019
pkg Gloo mtls cli (#289) Mar 26, 2019
test Gloo mtls cli (#289) Mar 26, 2019
.gitignore Delete build-cli (#257) Mar 15, 2019
Gopkg.lock Gloo mtls cli (#289) Mar 26, 2019
Gopkg.toml Gloo mtls cli (#289) Mar 26, 2019
Makefile Cli create AWS secret (#282) Mar 21, 2019 Fix supergloo architecture image link (#273) Mar 19, 2019
cloudbuild.yaml Gloo mtls cli (#289) Mar 26, 2019
generate.go checking correct versions of gloo and solo-kit (#262) Mar 15, 2019 Fix cli install (#202) Mar 5, 2019

The Service Mesh Orchestration Platform

SuperGloo, an open-source project to manage and orchestrate service meshes at scale. SuperGloo is an opinionated abstraction layer that will simplify the installation, management, and operation of your service mesh, whether you use (or plan to use) a single mesh or multiple mesh technologies, on-site, in the cloud, or on any topology that best fits you.

Installation   |   Developers   |   Documentation   |   Blog   |   Slack   |   Twitter

SuperGloo Architecture


Why SuperGloo?

SuperGloo helps users kick off their service mesh experience. Users who contemplate working with service mesh can be deterred by the many configuration choices they have to make. SuperGloo solves this problem by providing an opinionated API that automates the installation process, obviating the need for writing and deploying complicated yaml files.

SuperGloo takes charge of key functionalities associated with the mesh, including encryption, telemetry, and tracing. Launching any of these with SuperGloo is as simple as flipping a switch, completely bypassing the need for complicated configuration steps.

SuperGloo unifies management of ingress traffic (“north/south”) and mesh traffic (“east/west”). Every service mesh relies on ingress controllers to manage traffic across clusters and from the internet. SuperGloo provides a fully-automated opinionated workflow for configuring your mesh to work with your ingress, offering a unified management experience for all traffic.

SuperGloo gives you the freedom to pair any service mesh with any ingress. The mesh abstraction provided by SuperGloo allows users to choose their favorite mesh and ingress. In addition, it handles the installation and configuration necessary to allow them work together. SuperGloo also supports running multiple ingress with multiple mesh in the same cluster.

SuperGloo makes it easy to explore different meshes and migrate between them. The unified interface, as well as the automated installation, makes the transition from one mesh to another fast and painless.

SuperGloo allows use of the same tools with different meshes. The abstraction we seek to provide will allow developers to build a single product that runs on any mesh, or across meshes. For users, this will provide the ability to migrate between service mesh providers without changing the tooling they work with.

SuperGloo will ‘glue’ meshes of any type into a multi-mesh. For companies that run multiple service mesh instances, SuperGloo will connect all the different meshes together, across namespaces, across clusters, or across clouds. All with flat-networking and policy applied at every level, rather than repeated at each individual level, without the effort of synchronizing config across meshes.


Dead Simple API - Most service meshes are built with a complex API intended to support a vast number of use cases. SuperGloo boils down service mesh config to the basics, while being expressive about the features that are most important to users.

Installation - Install, Uninstall and Reinstall service meshes with default or customized settings. Automate complicated workflows such as supporting multi-tenant (multi-namespace) installations using the one-click SuperGloo API.

Discovery - Discover existing service mesh installations and integrate SuperGloo on top of them seamlessly, with no risk of error, and zero additional user configuration necessary.

Security - Manage Root Certificates, enable/disable mTLS, and enforce policy within your mesh with the click of a button.

Routing Traffic control - Apply sophisticated HTTP/2 features to any/all traffic in your mesh, such as traffic shifting, fault injection, header manipulation, and more.

Routing Resilience - Outlier detection, connection pooling, timeouts and retries.

Observability Metrics - SuperGloo automatically configures existing Prometheus, Grafana, and Jaeger installations to scrape and visualize data from your mesh. No more editing large YAML files and kubernetes configmaps!

Ingress Integration - Seamlessly install and configure any ingress to work with your mesh, all while configuring them with a unified management API.

Ingress discover - Discover an installed ingress and manage it.

Plugability - Highly extensible open-source Go architecture with development SDKs making it easy to extend SuperGloo with new features and meshes.

Features Snapshot

Istio AWS App Mesh Consul Connect Linkerd 2
Discovery 🚧 🚧 🚧 🚧
Security Root Cert N/A 🚧
mTLS N/A 🚧
Policy 🚧 N/A
Routing Traffic Control N/A N/A
Resilience N/A N/A N/A
Observibility Metrics via Prometheus N/A
Metrics via Grafana 🚧 N/A 🚧
OpenTracing 🚧 N/A 🚧
Ingress Installation 🚧 🚧 🚧 🚧
Discovery 🚧 🚧 🚧 🚧


Service Mesh Discovery
Linkerd 2 encryption
Ingress install
Ingress discovery
Metrics via Grafana


At Solo, we believe that companies at any stage of service mesh adoption can benefit from the ability to use multiple meshes simultaneously. At the early stages of adoption, users will benefit from the ability to experiment with multiple technologies. In addition, groups within the same organization may favor different options, making multi-mesh a lasting reality. Whether multi-mesh is a transition-phase or the end-game, keeping your options open without compromising on ease-of-use, functionality or flexibility will give early adopters a competitive edge.

Our vision is to enable multi-mesh: the ability to connect meshes of any type together, across namespaces, across clusters, and across clouds. All with flat-networking and policy applied at the super-mesh level, rather than repeated at each individual level, without the effort of synchronizing configs across meshes. The abstraction we seek to provide will allow developers to build a single product that runs on any mesh, or across meshes.


SuperGloo would not be possible without the valuable open-source work of projects in the service mesh community. We would like to extend a special thank-you to Istio, AWS App Mesh, Hashicorp Consul and Linkerd, as well as the vibrant Kubernetes community.

You can’t perform that action at this time.