Installation
This section describes how to install/uninstall Open Service Mesh (OSM) on a Kubernetes cluster
The OSM project builds on the ideas and implementations of many cloud native ecosystem projects including Linkerd, Istio, Consul, Envoy, Kuma, Helm, and the SMI specification.
OSM runs an Envoy based control plane on Kubernetes, can be configured with SMI APIs, and works by injecting an Envoy proxy as a sidecar container next to each instance of your application. The proxy contains and executes rules around access control policies, implements routing configuration, and captures metrics. The control plane continually configures proxies to ensure policies and routing rules are up to date and ensures proxies are healthy.
OSM is under active development and is NOT ready for production workloads.
Please search open issues on GitHub, and if your issue isn’t already represented please open a new one. The OSM project maintainers will respond to the best of their abilities.
Specification Component | Supported Release | Comments |
---|---|---|
Traffic Access Control | v1alpha3 | |
Traffic Specs | v1alpha4 | |
Traffic Split | v1alpha2 | |
Traffic Metrics | v1alpha1 | 🚧 In Progress #379 🚧 |
This section describes how to install/uninstall Open Service Mesh (OSM) on a Kubernetes cluster
Quickstart for Open Service Mesh (OSM)
Upgrade Guide
Uninstall
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.