FSM (Flomesh Service Mesh)

FSM (Flomesh Service Mesh) with Pipy proxy at its core is Kubernetes North-South Traffic Manager and provides Ingress controllers, Gateway API, and cross-cluster service registration and service discovery. Thanks to Pipy's “ARM Ready” capabilities, FSM is well suited for cloud and edge computing.

Introduction

This chart bootstraps a FSM deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

• Kubernetes 1.19+

Installing the Chart

To install the chart with the release name fsm run:

$ helm repo add fsm https://charts.flomesh.io
$ helm install fsm fsm/fsm --namespace flomesh --create-namespace

The command deploys FSM on the Kubernetes cluster using the default configuration in namespace flomesh and creates the namespace if it doesn't exist. The configuration section lists the parameters that can be configured during installation.

As soon as all pods are up and running, you can start to evaluate FSM.

Uninstalling the Chart

To uninstall the fsm deployment run:

$ helm uninstall fsm --namespace flomesh

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

Please see the values schema reference documentation for a list of the configurable parameters of the chart and their default values.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install fsm fsm/fsm --namespace flomesh --create-namespace \
  --set fsm.image.pullPolicy=Always

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install fsm fsm/fsm --namespace flomesh --create-namespace -f values-override.yaml